Organic Maps: Offline Navigation App Taking HN by Storm

I’ve been looking for a reliable offline navigation app for years. Google Maps eats battery and data, and proprietary lock-in feels wrong. So when I saw Organic Maps climbing the Hacker News front page with 179 points and 50 comments, I had to dig in.

The Story Behind Organic Maps

Organic Maps is an open-source, offline-first maps application that uses data from OpenStreetMap (OSM). It’s a lightweight alternative to Google Maps, designed to work completely offline after downloading regional map files. The app is available on both iOS and Android, and can be installed via F-Droid or directly from the website.

The project started as a fork of MapsWithMe, an earlier open-source maps app. It focuses on privacy—no tracking, no ads—and allows users to edit map data directly through the app, contributing corrections back to OSM.

But the HN discussion reveals more than just praise. There’s a fork called CoMaps, created over governance concerns. And some users have flagged that the app includes non-open-source compiled binary data files, raising questions about its true open-source nature.

Why Organic Maps Is Gaining Traction on HN

The thread is full of genuine enthusiasm from users who’ve actually relied on Organic Maps in the field. One commenter wrote:

“Organic Maps was my go to app for a navigation app where you can fix errors yourself immediately! So much better than having to work for free on the proprietary apps, and hope they accept your edits.”

Another shared a practical use case:

“I use OrganicMaps a lot for long walks and it's great. Works perfectly offline if you have downloaded the map of the region beforehand, which is helpful if you are in an area with poor reception or just want to conserve phone battery by turning off data.”

But the conversation isn’t all glowing. A skeptical commenter pointed out:

“This app contains non open source components - compiled binary data files (including but not limited to .mwm map files) under a non FLOSS license.”

This led to confusion about licensing, and the mention of a fork—CoMaps—was introduced by another user:

“There is also CoMaps which is a fork of Organic Maps, after concern over the governance of Organic Maps.”

The existence of CoMaps shows that even in the open-source community, trust and governance matter deeply.

Why Organic Maps Matters for Privacy and Open Source

Organic Maps is a genuinely useful app for people who need offline maps. But the HN thread highlights two perennial tensions in open-source: licensing purity vs. practical utility, and governance vs. leader-driven development.

First, the non-open-source map files. Yes, the map data (OSM) is open, but the compiled .mwm binaries are not. The developers likely include them for performance, but that breaks the FLOSS promise for some users. It’s a trade-off. If you care about fully libre software, you might prefer rendering the tiles yourself (which some alternatives do). But for most users, the app works great.

Second, the fork CoMaps. Forks can signal a healthy community, but they can also split limited resources. CoMaps is adding CarPlay support and working on modernizing the codebase—features that Organic Maps hasn’t prioritized. This is how open-source ecosystems evolve, but it also means users have to choose.

The real value here is that Organic Maps proves offline, OSM-based navigation is viable. The privacy angle is strong. The editability is empowering. But the project’s future depends on how it navigates governance and licensing. I hope it gets the developer attention it needs.

What Organic Maps Means for Developers Building Offline Apps

If you’re building a navigation feature or a mapping tool, you can learn from Organic Maps’ approach. First, consider offline-first design: many users have unreliable connections. Second, using OSM data gives you flexibility, but you need to handle tile rendering and storage carefully.

A simple way to fetch OSM data programmatically is the Overpass API. For example, to query bus stops in a small area:

curl -X POST https://overpass-api.de/api/interpreter \
  -d 'data=[out:json];node(51.5,-0.1,51.5,-0.0)[highway=bus_stop];out;'

This returns JSON you can parse into your app. For full offline maps, consider using MapLibre GL to render vector tiles from OSM data. It’s the modern, open alternative to proprietary SDKs.

The fork CoMaps also shows that community governance matters. If you start an open-source project, clearly document your governance model.

Should You Use Organic Maps?

If you value privacy, offline functionality, and the ability to contribute to map data, yes, you should try Organic Maps—or CoMaps if you want CarPlay. If you rely on real-time traffic or turn-by-turn navigation in complex urban environments, stick with mainstream apps. But for hiking, cycling, and backroad adventures, Organic Maps is a solid choice. And if you’re a developer, the discussion around licensing and governance is a timely reminder that open-source is about more than just code.