The editorial argues that Organic Maps, shipped by a five-person volunteer team in their spare time, is objectively better than Google Maps for travelers on core metrics. The renewed HN attention reflects a recognition that a focused non-profit fork can outperform a division of engineers when incentives aren't warped by ads and account walls.
By resubmitting Organic Maps to HN and driving it to 899 points more than a year after the first front-page appearance, tosh is implicitly endorsing the position that this small-team offline app deserves ongoing attention as a viable alternative to Google Maps.
The editorial frames Organic Maps' resurgence as a signal of a broader vibe shift: GDPR enforcement biting harder, iOS 18 exposing Google's location-history collection, and the local-first software movement gaining momentum. An app that phones home to no one lands very differently in 2026 than it did in 2021.
The editorial calls Organic Maps a masterclass in scoping down a hard problem: compressing a 150GB OpenStreetMap planet file down to 400MB for France or under 5GB for the entire continental US by throwing away everything hikers and drivers don't need and quantizing coordinates to target zoom levels. The column-oriented, mmap-friendly MWM format enables instant search across 12 million offline POIs — a small team's win because they ruthlessly narrowed the problem.
Organic Maps re-hit the front page of Hacker News with 899 points, more than a year after its initial fork from Maps.me made the same rounds. The renewed attention has less to do with a new release than with a quiet realization sweeping through developer Twitter and Mastodon: the app that a five-person volunteer team ships in their spare time is, on the metrics that actually matter to travelers, better than what Google Maps does with a division of engineers.
The app is a fork of Maps.me, forked in late 2020 by the original engineering team after Daegu-based Mail.ru sold the property and pivoted the codebase toward ads and account walls. The core team walked, took the AGPL-licensed code with them, and started shipping under a Czech non-profit. The rendering engine is C++, the data pipeline processes OpenStreetMap dumps into a proprietary compact binary format called MWM, and the whole thing runs offline after a one-time regional download.
What's new in 2026 is context. Between GDPR enforcement biting harder, iOS 18's location-history transparency features exposing just how much Google keeps, and the general vibe shift toward local-first software, an offline map app that phones home to no one is landing differently than it did in 2021.
The technical achievement is worth walking through, because it's a masterclass in scoping a hard problem down to something a small team can actually ship. OpenStreetMap's raw planet file is roughly 150GB compressed. Organic Maps ships France in about 400MB, California in 250MB, and the entire continental US in under 5GB. They get there by throwing away everything a hiker or driver doesn't need — historical building outlines, most metadata, contributor attribution — and quantizing coordinates down to what's meaningful at their target zoom levels.
The MWM format they emit is column-oriented and mmap-friendly, which is why search feels instant even when you're browsing 12 million POIs offline. Compare this to Google Maps, which despite years of "offline mode" still degrades noticeably without a connection, can't search POIs by category offline, and quietly re-downloads region data every 30 days whether you asked it to or not.
The economics are the second interesting thread. Organic Maps runs on about €80k/year, funded by donations and one Kickstarter, and their entire infra bill is dominated by CDN egress for map downloads. They don't have to run routing servers, geocoding servers, or telemetry pipelines. When you tap "navigate to," the routing happens on your device using a locally-cached graph. This is the same architecture pattern that projects like GraphHopper and Valhalla explored on the server side — Organic Maps just shipped the client-side version and won.
Community reaction on HN split predictably. The top comment praised the search UX; the second-highest complained that POI freshness lags Google by months, which is true — you're only as current as your last regional download plus whatever OSM contributors happened to touch that area. Restaurants close, roads change, and Organic Maps won't know until you refresh. For a daily-driver navigation app in a city you live in, that's a real limitation. For travel, hiking, cycling, or driving through anywhere with spotty cell coverage, it's not.
The practitioner takeaway isn't "install Organic Maps" — though you probably should if you travel. It's that offline-first architecture, dismissed for a decade as an anachronism from the pre-4G era, is quietly having its moment again, and Organic Maps is the case study to point at when someone on your team wants to justify running everything through a server.
The pattern generalizes. Local-first sync engines (Automerge, Yjs), on-device inference (Whisper.cpp, llama.cpp), and edge databases (SQLite going everywhere, DuckDB in the browser) are all riding the same wave. The economics that made "just put it in the cloud" the default answer in 2015 have shifted. Phones have 8+ cores and 8GB of RAM. Storage is essentially free at consumer scale. Meanwhile, cloud egress costs are up, cell coverage in a lot of the world is worse than developers assume, and users have gotten wise enough about tracking to notice which apps ask for background location.
If you're building a mobile app in 2026 and your data model is under, say, a few gigabytes for the largest reasonable user, there's a serious case for shipping the data instead of the query. Your app gets faster (no network round-trip), cheaper to run (no per-request infrastructure), and dramatically more resilient to your own downtime. The tradeoffs — staleness, update logistics, upfront download UX — are real but solvable. Organic Maps solved them by making the download flow explicit and letting users pick regions.
The AGPL choice matters here too, and it's worth thinking about if you're evaluating a fork strategy. AGPL on a client-side app is a deterrent, not a lock — it means anyone who ships a modified version has to publish their changes, which killed the ad-supported fork that Mail.ru presumably would have preferred to ship. It's an underrated tool for keeping a project honest.
The question that matters isn't whether Organic Maps will overtake Google Maps — it won't, and it doesn't need to. It's whether the offline-first pattern it demonstrates will influence how the next generation of mobile apps get built. The infrastructure to do local-first well — CRDTs, sync engines, embedded databases, on-device ML — has never been more mature. The economic pressure to stop paying AWS for things that could run on the user's phone has never been higher. Organic Maps is a five-person team's proof-of-concept that the whole world fits, if you're willing to think about what you actually need.
There is also CoMaps (https://www.comaps.app/) which is a fork of Organic Maps, after concern over the governance of Organic Maps https://itsfoss.com/news/organic-maps-fork-comaps/
I would recommend people use comaps instead which is the actual FOSS fork. OM has a long history of malicious behaviour like quietly adding ads, turning a part of its previously open sourced code proprietary and misappropriating donations. OM has lost most of its community a year ago to comaps and a
The quality of the maps is getting better, much more useful and detailed than Google Maps. I find it much easier to locate myself on Organic Maps than Google Maps. For example parks are only a green blob on Google Maps, while benches, walking paths, drinking water points, toilets and other landmarks
To the best of my knowledge, Organic Maps is a dying project.CoMaps was forked from Organic Maps because of shift in how things were being done and ignored. I mean, those in IT know very well how that is ending.CoMaps is highly active and receiving new features release by release.If you wanna use a
Top 10 dev stories every morning at 8am UTC. AI-curated. Retro terminal HTML email.
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 editsThere’s a fork from one year ago, CoMaps, that is gaining different featuresE.g., I am adding CarPlay