Project ideas from Hacker News discussions.

CoMaps – FOSS Offline Maps

📝 Discussion Summary (Click to expand)

Summary of the 3 most prevalent themes

Theme Representative quotations
1. Governance & transparency worries “Despite being advertised as a community‑driven project, key decisions, including financial management, partnerships (with Kayak, for instance), and the inclusion of proprietary components in the code were made by a small group of shareholders, often without input from the broader contributor community.” — miroljub
2. Search and POI data limitations “My biggest issue with OrganicMaps is that the search isn’t very good. It really struggles to find my destination sometimes.” — dopidopHN2
3. Preference for CoMaps’s usability & update cadence “CoMaps works great. You get notified in the app to download the updated maps you selected every 2 weeks or so. Could be wildly different than that, just what I notice.” — Cider9986

🚀 Project Ideas

Generating project ideas…

OpenStreetMap Search Hub

Summary

  • A self‑hostable, fuzzy‑matching search service for OSM places that fixes the poor search experience reported in the HN thread.
  • Users get accurate, instant matches without relying on Google‑scale data.

Details

Key Value
Target Audience Developers and OSM enthusiasts who need reliable place lookup for mobile and desktop mapping apps
Core Feature Context‑aware search with synonym expansion, multi‑language support, and filterable categories
Tech Stack Python/Flask backend, PostgreSQL/PostGIS, Elasticsearch/Phenosearch, Docker deployment
Difficulty Medium
Monetization Revenue-ready: SaaS tiered pricing (free tier up to 10k queries/month, paid plans starting at $9/mo)

Notes

  • HN commenters repeatedly complained that “search isn’t very good” and “struggles to find my destination”; solving this would directly address a top pain point.
  • The project could be packaged as a simple API endpoint that any map client (CoMaps, Organic Maps, OsmAnd) can query, enabling instant migration without rebuilding search logic.

MapLayers – Modular Overlay Engine

Summary

  • A plugin‑friendly map rendering framework that lets users add custom data layers (traffic, accessibility, hiking routes, POI metadata) via a standardized API.
  • Solves the lack of overlay support and extensibility highlighted by multiple HN comments.

Details

Key Value
Target Audience OSM contributors, developers of navigation apps, and power users who want custom map features
Core Feature Pluggable layer system with versioned schema, auto‑hosted tile server, and UI widget for layer selection
Tech Stack TypeScript/React front‑end, Node.js backend, Mapbox GL JS, PostgreSQL for layer storage, WebAssembly for fast processing
Difficulty High
Monetization Hobby

Notes

  • Community members asked “Any app that supports overlays?” and pointed out missing subway/traffic layers; providing a shared layer marketplace would fill this gap.
  • The project could host a free tier of common layers (e.g., public transit routes) while offering premium custom layers for enterprises, encouraging open‑source contributions.

TileSync – Decentralized Offline Tile Sync & Cache

Summary

  • A peer‑to‑peer sync service that automatically updates OSM vector tiles on‑device, bypassing the tile‑cap limits that frustrate users of Organic Maps and CoMaps.
  • Delivers fresh map data without requiring manual downloads or paid subscriptions.

Details

Key Value
Target Audience End‑users of offline‑first map apps and contributors who want up‑to‑date maps on low‑bandwidth connections
Core Feature Automatic delta‑diff sync using CRDTs, configurable cache size, and optional anonymous sharing via IPFS
Tech Stack Rust backend, SQLite/FactorDB, libosmium for OSM parsing, IPFS for distribution, Electron/Tauri for desktop clients
Difficulty Medium
Monetization Revenue-ready: subscription for premium sync speeds and priority updates ($5/mo)

Notes

  • Several users noted “slowness to calculate a direction” and “maps update months later,” indicating demand for fresher, faster tile delivery.
  • By integrating with existing map apps via a lightweight connector library, TileSync could become the default offline tile source, directly addressing the “tile cap” and “update frequency” frustrations.

Read Later