← Back to Blog

The EF-Map Journey: From First Commit to 1,116 Commits in 137 Days

On August 12, 2025, the first commit was pushed: "Initial commit." Just 137 days later, EF-Map has grown into a comprehensive EVE Frontier mapping ecosystem with 1,116 commits, 55,000 lines of frontend code, real-time blockchain indexing, a native Windows overlay, and features that push the boundaries of what a community-built game tool can achieve. This is the story of that journey—told through the commits themselves.

1,116
Total Commits
137
Days of Development
55K
Lines of Code
8.1
Commits Per Day
6.1M
Lines Added
1.9M
Lines Removed

The raw numbers tell part of the story: an average of 8.1 commits per day, with peaks reaching 40+ commits during intense feature sprints. But the true narrative emerges when you trace the evolution month by month—from basic camera controls to AI-powered natural language commands, from simple starfield rendering to real-time blockchain event streaming.

The Development Methodology: Vibe Coding

Before diving into the timeline, it's important to understand how EF-Map was built. The project creator has zero traditional coding experience. Every line of TypeScript, Python, C++, and SQL was written through "vibe coding"—describing intent in natural language to LLM agents (primarily GitHub Copilot in agent mode) that translate those intentions into working code.

This methodology explains the commit patterns: rapid iteration, immediate fixes, and the ability to pivot quickly when features don't work as expected. A typical development session might generate 20+ commits as the human describes what they want, the AI implements it, testing reveals issues, and the cycle repeats until the feature works correctly.

August 2025: Foundation (323 Commits)

The first month was explosive—323 commits in just 20 days, establishing every core system that would later be refined.

Week 1: The Core Map (Aug 12-18)

August 12

Day 1: Two initial commits, followed immediately by "feat: Implement core map interactions and selection." The foundation was laid: a Three.js scene with stars, stargates, and basic mouse interaction.

August 13

Camera Revolution: "replace OrbitControls with camera-controls for true turntable yaw" and "enable damping and remove axis controls." The space-appropriate camera behavior that users experience today was established on day 2.

August 14

Database Integration: "Fix Netlify build errors for sql.js integration"—the critical SQLite-in-browser approach that lets the app run without a backend was implemented within 48 hours.

August 15-17

Selection & Routing: Star selection accuracy fixes, region highlighting, planet count legends, and the first routing implementation: "feat(routing): implement point-to-point routing."

Week 2-3: Advanced Routing & Scout Optimizer (Aug 19-28)

The Scout Optimizer—one of EF-Map's signature features—emerged during this period through intense iteration:

The commit messages from Aug 20 tell the story of real-time problem-solving: "fix: guard 2-opt to avoid introducing unreachable segments," "feat: add debug mode with detailed NN/2-opt logging for failing test cases," "fix: refine NN bridging to only use tail."

Cinematic Mode Emerges (Aug 24-25)

What started as a visual enhancement became one of EF-Map's most beloved features:

The iterative refinement is visible: "fix: remove background mesh on disable to restore interactions," "fix: aggressively restore star material & colors on disable"—each fix discovered through testing, implemented within minutes.

Month-End Feature Explosion (Aug 29-31)

The final days of August added major user-facing features:

August by the Numbers

  • 323 commits in 20 days (16.15 commits/day average)
  • Core systems established: routing, cinematic, panels, persistence
  • First PR merged: #1 (TS build error fixes, Aug 15)
  • Last PR of month: #38 (session & cinematic metrics)

September 2025: Polish & Infrastructure (252 Commits)

September shifted focus from raw features to infrastructure, visual polish, and the foundations of what would become the desktop overlay.

Visual Refinement (Sep 1-3)

The first week was dedicated to making the map visually stunning:

Station Integration & Region Stats (Sep 3-4)

Game data integration deepened:

The Transmission System (Sep 4)

One of the most whimsical features emerged—the ambient radio transmission system that gives EF-Map its personality:

Cloudflare Migration Begins (Sep 19-28)

A critical infrastructure shift started mid-month—moving from Netlify to Cloudflare Pages + Workers:

Smart Assemblies Foundation (Sep 24)

The blockchain-indexed structure system that would become central to the platform was architected:

September by the Numbers

  • 252 commits—focused on polish and infrastructure
  • Cloudflare migration initiated (completed in October)
  • Smart Assemblies, region stats, transmissions added
  • Display Settings panel with user customization

October 2025: The Quiet Month (54 Commits)

October had the fewest commits—just 54—but they were transformative. This was the month of the desktop overlay.

Overlay Helper Bridge (Oct 1-30)

The commits tell the story of a parallel development effort in the ef-map-overlay repository:

The web app side integrated with the native helper:

Tribe Bookmarks E2E Encryption (Oct 22)

A significant security feature was implemented:

Microsoft Store Publication

The overlay helper was published to the Microsoft Store:

October by the Numbers

  • 54 commits—quality over quantity
  • Desktop overlay helper published to Microsoft Store
  • E2E encryption for tribe bookmarks
  • Helper bridge integrated with web app

November 2025: The Expansion (340 Commits)

November was the busiest month—340 commits—with major architectural improvements and feature additions.

Solar System View (Nov 6-9)

A complete new view mode was implemented:

The database work that enabled this was substantial—migrating from Phobos to FrontierData extraction pipeline, building a 67MB solar system database with 28 columns, 236K celestials, and 417K Lagrange points.

Code Architecture Refactoring (Nov 19-21)

The 10,000-line App.tsx was modularized:

21 custom hooks were extracted, making the codebase maintainable despite its size.

AI Commands Integration (Nov 26)

Natural language control came to EF-Map:

Live Universe Events (Nov 28-29)

Real-time blockchain streaming was implemented using Cloudflare Durable Objects:

November by the Numbers

  • 340 commits—the most active month
  • Solar system view with 67MB celestial database
  • 21 custom React hooks extracted
  • AI natural language commands
  • Live blockchain event streaming

December 2025: Maturity (147 Commits to Date)

December represents the project reaching maturity—fewer core features, more refinement and user-facing polish.

Killboard & PvP Tracking (Dec 3)

Infrastructure Improvements (Dec 4-6)

The backend moved to the cloud:

Performance Optimization (Dec 8-9)

Seasonal Features (Dec 14)

Blueprint Calculator (Dec 12-16)

Unified Smart Panel (Dec 26)

The latest major feature consolidated multiple panels:

December by the Numbers (Through Dec 27)

  • 147 commits—steady refinement
  • Killboard with PvP leaderboards
  • VPS migration to Hetzner cloud
  • 14.6x routing performance improvement
  • Blueprint Calculator for production planning
  • Seasonal winter effects

The Architecture Today

After 1,116 commits, EF-Map's architecture reflects its iterative evolution:

Frontend (55,000 Lines)

Backend (Cloudflare)

Infrastructure (Hetzner VPS)

Desktop (ef-map-overlay Repository)

Commit Patterns & Insights

The Intensity Curve

Month Commits Per Day Focus
August 323 16.2 Core systems, routing, cinematic
September 252 8.4 Polish, infrastructure, Cloudflare
October 54 1.7 Desktop overlay (parallel repo)
November 340 11.3 Solar view, AI, live events
December 147 5.4 Killboard, blueprints, refinement

Common Commit Prefixes

The commit message conventions reveal development patterns:

The Fix-After-Feat Pattern

A notable pattern in vibe coding: features are often followed immediately by fixes. This isn't a sign of poor quality—it's the natural result of rapid iteration where the AI implements, testing reveals edge cases, and fixes follow within minutes:

feat(solar-system): implement smooth camera transitions
fix(solar-system): suppress star interactions in solar system view
fix(solar-system): delay camera animation until scene fully loads
fix(solar-system): position solar system at star's universe coordinates

What's Next?

The commit history doesn't end here. As of December 27, 2025, EF-Map continues to evolve with active development on:

Explore the Commit History

The full commit history is available on the Patch Notes page, where you can browse all 1,116 commits with their full messages and dates.

Related Posts

EVE Frontierproject historycommit historyvibe codingLLM developmentThree.jsCloudflareblockchainopen sourcedevelopment journey