Developer builds flight comparison tool with Claude Code using BDMA approach

A developer shared their experience building easyscape.eu using Claude Code, emphasizing the practical challenges of getting users rather than just building the product.
Development Approach
The creator used Claude Code with a BDMA (build/debug/measure/adjust) approach, running this loop daily. They emphasized: "Pas de magie. Juste de l'itération." (No magic. Just iteration.)
Product Details
easyscape.eu addresses a specific flight comparison problem: most people only check one departure airport, while the best deal is often elsewhere. The tool:
- Compares multiple departure airports
- Integrates real costs (road, tolls, parking)
- Shows the most economical departure, not just the cheapest ticket
The creator noted: "Ça paraît évident. Mais en pratique, c'est loin de l'être." (It seems obvious. But in practice, it's far from it.)
User Acquisition Challenges
The developer discovered that building the product was easier than getting people interested. They posted on Reddit and Facebook, tested formats, and explained the concept repeatedly, experiencing a pattern of: "petit pic → plus rien → doute → on recommence" (small spike → nothing → doubt → start over).
What actually worked was direct exchanges: responding to people, explaining, and adapting based on feedback. For example:
- When users asked for one-way flights, they implemented it that week
- When users mentioned airport zones, they worked on it
The developer observed: "Tu peux construire beaucoup. Optimiser énormément. Te dire que tu avances. Mais si les gens ne comprennent pas instantanément la valeur, il ne se passe rien." (You can build a lot. Optimize enormously. Tell yourself you're making progress. But if people don't instantly understand the value, nothing happens.)
Current Status
While not having huge numbers, the developer now has real users who test, report savings, and return. They noted: "Ce n'est plus juste une idée dans ta tête. Ça devient quelque chose qui sert vraiment à quelqu'un." (It's no longer just an idea in your head. It becomes something that really serves someone.)
Advice for Builders
- Don't seek perfection
- Don't overthink your visibility
- Don't be afraid to repeat your message
- Don't expect things to go fast
The developer concluded: "Si quelques personnes commencent à s'y intéresser, tu es déjà bien plus loin que la majorité des projets qui ne dépassent jamais le stade de l'idée." (If a few people start to be interested, you're already much further than the majority of projects that never get past the idea stage.)
📖 Read the full source: r/ClaudeAI
👀 See Also

Claude Code vs Codex: A Builder's Workflow Split
A developer shares practical split: Claude Code for focused repo work with clean diffs, Codex for messy cross-tool tasks involving browser, docs, and app testing.

Hermes vs. OpenClaw: The Difference Is Personality, Not Speed
A developer compares Hermes and OpenClaw side by side and finds the key difference is how each handles identity: Hermes stores memories, OpenClaw stores personality facets via soul.md.

Claude AI Agents Build Simulator, Optimize Game Algorithm to Beat Human Score
A developer tested Claude AI agents on the programming game The Farmer Was Replaced by having them build a Python simulator of the game, then iteratively develop a sunflower harvesting algorithm. The AI achieved a time of 5:21, beating the developer's personal best and reaching rank 30 on the global leaderboard.

Case Study: Using Multiple AI Agents to Build a Production C++ Library
A developer documented a multi-month process using four AI agents (Claude, ChatGPT, Gemini, Grok) with distinct roles to build FAT-P, a header-only C++20 library with 107 headers and zero external dependencies. The system included cross-review, governance documents written by AI, and a demerit tracker to encode failure modes.