CoMaps: the OpenStreetMap client that ships without a CEO drama arc

5 min read 1 source clear_take
├── "CoMaps matters most as a governance experiment, not as a consumer app"
│  └── top10.dev editorial (top10.dev) → read below

The editorial argues that framing CoMaps as 'another Google Maps alternative' undersells the story. The unusually blunt pitch — 'we forked because we didn't want one person to be able to sell this again' — combined with a formal Belgian association and co-op-style governance makes this a test case for whether FOSS projects can structurally prevent the Maps.me-style commercial capture that keeps repeating in this lineage.

├── "OSM's real problem is developer ergonomics, not data quality"
│  └── top10.dev editorial (top10.dev) → read below

The editorial contends OSM adoption is bottlenecked by the gap between raw open data and shippable features. An 80+ GB planet.osm dump plus PostGIS, osm2pgsql, Mapnik/Tegola/MapLibre, and OSRM/Valhalla/GraphHopper preprocessing pipelines mean a working engineer can't build on OSM by Friday — and CoMaps only masks that problem for end users rather than solving it for developers.

├── "CoMaps is a straightforward win: a no-tracking, no-ads offline maps app that just works"
│  └── @basilikum (Hacker News, 461 pts) → view

The submitter surfaced CoMaps to 461 points by framing it as exactly what its homepage says — FOSS offline maps with OpenStreetMap data, no accounts, no tracking, no ads, on Android and iOS. The strong upvote signal reflects an HN audience that treats this as a consumer app story worth celebrating on its own terms, independent of governance debates.

└── "Hosting on Codeberg instead of GitHub is a deliberate values statement"
  └── top10.dev editorial (top10.dev) → read below

The editorial flags the Codeberg choice as 'small but pointed' — a project that forked over governance and commercial-capture concerns is unlikely to host its source on a Microsoft-owned platform. It signals the same anti-enclosure ethos as the co-op governance model and the no-ads/no-tracking product stance.

What happened

CoMaps hit #1 on Hacker News with 461 points — a fork of Organic Maps, which was itself a fork of Maps.me after MapsWithMe pivoted toward ads. The project's homepage is refreshingly literal: offline maps, OpenStreetMap data, no tracking, no accounts, no ads. It ships for Android and iOS, with source on Codeberg rather than GitHub — a small but pointed choice.

The backstory matters more than the app itself. Organic Maps was already the go-to FOSS OSM client, but its maintainers publicly split in late 2024 over governance, trademark control, and disagreements about direction. CoMaps is the outcome: a new brand, a formal association being set up in Belgium, and an explicit commitment to co-op-style governance. The pitch is unusually blunt for an open-source project: we forked because we didn't want one person to be able to sell this again.

Under the hood it's the same lineage as Maps.me — a C++ core, custom vector tile rendering, offline routing via a fork of OSRM, search built on OSM tags. Country-sized map packs weigh in around 10–200MB. Turn-by-turn works without a SIM. Bicycle and hiking routing exists but is uneven, exactly as OSM data is uneven.

Why it matters

For most HN readers this is a consumer app story: another Google Maps alternative for people who don't want Google in their pocket on a hike. That framing undersells it. The more interesting story is what CoMaps signals about the OpenStreetMap ecosystem — and where it's still stuck.

OSM has had a persistent adoption problem that isn't about data quality: it's about the distance between "the data is open" and "a working engineer can ship a feature on it by Friday." The raw planet.osm dump is 80+ GB of XML. Turning that into tiles requires PostGIS, osm2pgsql, a renderer (Mapnik, Tegola, or the newer MapLibre vector stack), and a tile server. Routing requires OSRM, Valhalla, or GraphHopper — each with its own preprocessing pipeline measured in hours and disk in tens of gigabytes. Geocoding requires Nominatim or Photon. None of these come with a hosted free tier that a startup can actually build on without hitting a wall.

That's the systemic gap CoMaps quietly illustrates. The app works because a small team spent years wrangling that toolchain into something shippable. But if you're a backend dev who wants to add "find nearby" or "route from A to B" to your product tomorrow, the FOSS path is still: read six blog posts, provision a 32GB box, wait four hours for a preprocessing job, and hope your users don't want Alaska. Publishing a firehose of geodata isn't the same as shipping an ecosystem — and until OSM has the equivalent of Stripe's docs and a free tier that survives your first Show HN, Mapbox and Google will keep collecting the rent.

CoMaps also lands in a specific political moment. Google Maps has been quietly degrading — removing features from the web version, pushing users to the app, tightening the Maps Platform pricing (the July 2024 pricing changes broke a lot of small projects). Mapbox pulled the same move in 2020 when it went closed-source with GL JS v2, which is what kicked off MapLibre. Foursquare open-sourced its POI dataset in 2024. Overture Maps — the Amazon/Meta/Microsoft/TomTom consortium — is now shipping monthly releases of a merged base map. The underlying stack is being rebuilt in the open faster than at any point in the last decade; the missing layer is developer experience, not data.

The community reactions on the HN thread are worth reading past the top comment. Practitioners who've actually shipped on OSM are consistent about two things: the data is good enough for 95% of use cases, and the tooling makes you earn it. Several point out that the Organic Maps / CoMaps split — while messy — is exactly the kind of governance stress-test OSS projects need to survive. Others note the obvious risk: two forks with near-identical codebases now split a small contributor pool.

What this means for your stack

If you're building anything that touches a map, the practical takeaways are narrower than the drama suggests.

If you ship a mobile app and want a maps SDK that isn't Google: MapLibre Native is the answer, not CoMaps. CoMaps is an end-user app, not a library. But its existence is a useful signal that the MapLibre + OSM stack is production-viable — a team of volunteers just shipped a polished consumer app on it. If you were waffling on adopting MapLibre for a mobile feature, this is one more data point that it works.

If you need routing or geocoding as an API: self-hosting Valhalla or OSRM is now genuinely tractable on a single beefy box for a country-sized region, and the Docker images are maintained. The economics flip against you the moment you need global coverage with sub-100ms p99 — that's where hosted services (Stadia Maps, Geoapify, Maptiler, or Mapbox itself) still win. Rule of thumb: if your maps bill is under $500/month, stay hosted; if it's over $5,000/month, the ops cost of self-hosting starts to pencil out.

If you care about privacy claims in your own product: CoMaps' architecture is a useful reference. No accounts, no telemetry, map data bundled or downloaded per-region, routing done on-device. That's a shippable template — not a research paper — for what "privacy-respecting location features" actually looks like as code.

Looking ahead

The honest read is that CoMaps itself will probably do fine — the same audience that installed Organic Maps will install CoMaps, and the association structure should prevent a repeat of the drama that spawned it. The bigger question is whether the wider OSM ecosystem uses this moment to close the developer-experience gap. Overture's monthly releases plus MapLibre's momentum plus a maturing self-host story is the closest the open geo stack has been to a real Google/Mapbox alternative for developers, not just end users. If someone ships the "Vercel for OSM" in the next 18 months — one command, hosted tiles + routing + geocoding, sane free tier — the map layer of the internet starts to look very different. If nobody does, CoMaps will remain what Organic Maps was: a beautiful app on top of infrastructure that most developers still can't afford to touch.

Hacker News 739 pts 189 comments

CoMaps – FOSS Offline Maps

→ read on Hacker News

// share this

// get daily digest

Top 10 dev stories every morning at 8am UTC. AI-curated. Retro terminal HTML email.