Organic Maps

Original Article ↗ Hacker News Discussion ↗

Overview & Use Cases

  • Organic Maps (OM) is praised as an offline, privacy-focused navigation app using OpenStreetMap (OSM) data, especially good for hiking, cycling, and travel in areas with poor connectivity.
  • Users rely on it for long walks, wilderness/backcountry driving, and international travel, often alongside Google Maps for businesses and traffic.

Organic Maps vs CoMaps & Governance Dispute

  • CoMaps is a fork of Organic Maps, itself a fork of Maps.me. Forking was driven by concerns over OM’s governance:
    • Use of donations for shareholders’ personal expenses without transparent accounting.
    • Addition of proprietary components and a custom non‑FOSS data license for map files and generator.
    • Experiments with referral “ads” (e.g., Kayak links).
  • Some argue donations should fund only clearly disclosed project costs; others say paying developers (including vacations) is legitimate.
  • One side claims OM is “dying” and users have “mass migrated” to CoMaps; others point to active OM releases and sizable communities and dispute that characterization.

Feature & UX Comparisons

  • CoMaps aims to be fully FOSS, non‑profit, and community‑governed, adding features like Android Auto, CarPlay, live traffic (in progress), OpenAddresses integration, and search tweaks.
  • OM is described as more mature in some map features (e.g., colored marked hiking/cycling routes), but newer parts are harder to fork due to closed tools.
  • OsmAnd is repeatedly cited as the power‑user alternative: very feature‑rich (routing profiles, nautical/topo, plugins) but complex and sometimes slow or battery‑hungry.
  • Many non‑technical users find OsmAnd “arcane” and prefer the simpler OM/CoMaps UI.

Data, Licensing & FOSS Purity

  • Several comments criticize OM’s non‑FOSS map data license and non‑public map generator, arguing it undermines the “right to fork.”
  • Others downplay this for typical users, who care more about functionality than governance disputes.

Strengths Highlighted

  • Offline-first design, low battery use (especially CoMaps), rich OSM POIs (trails, benches, water taps), easy on-the-spot map editing, and no tracking.
  • Particularly competitive for hiking/trails and in regions where Google/Apple maps are weak.

Limitations & Gaps

  • Major pain points:
    • Weaker address/business search and recency vs Google.
    • Lack of robust live traffic and incident-aware routing.
    • Missing or flaky track recording for some users.
    • No polished web client; desktop builds feel immature.
  • Some feel FOSS map apps remain fragmented, with duplicated efforts instead of consolidation on a single polished alternative.