I built a flight tracking tool because most existing ones felt too heavy for quick use

Hi everyone,

I love traveling, and for a long time I wanted a very simple way to track flights and visualize them on a map.

I tried a bunch of existing tools, but they all seemed to optimize for power users:

• account required upfront
• lots of fields I didn't always have
• slow or cluttered UIs when I just wanted a quick answer

What I really wanted was something closer to a calculator:
enter origin + destination → instantly see the route.

So I decided to build my own.

The main goal was speed and low friction. You only need the mandatory origin and destination to start, and you can add more details later if you want. I also wanted it to work offline, so even without an account it's still useful for quick exploration.

While building it, a few things surprised me:

• "simple" flight data gets complicated very fast
• offline support influenced way more design decisions than I expected
• most people care more about visual exploration than exact details

If you want to go further, you can create an account to save multiple flights, share an image of your map, see stats, or get AI-powered insights, but the core experience works without one.

It's still very much a work in progress, and I'm trying hard not to overbuild it.

If you're curious, this is what I've built so far: https://myflightroutes.com

I'd really appreciate any feedback:

• Is this something you'd personally use?
• Anything confusing or missing?
• Where would you draw the line between "simple" and "too limited"?

Happy to answer any questions about the build, tradeoffs, or mistakes so far.