StreetComplete on iOS is now in public beta

StreetComplete’s role and reception

• Seen as a very approachable way to contribute to OpenStreetMap (OSM), especially for non-technical users.
• Question/quest-based UI with photos and multiple choice lowers the barrier vs traditional editors.
• Several users report mapping meaningful local details (toilets, small roads, house numbers, opening hours) in minutes after years of not contributing.
• Some warn it is a “gateway” into heavier OSM editing with more advanced tools.

iOS public beta and UX feedback

• Many are excited that iOS support finally exists; it enables social mapping with mixed-platform groups.
• TestFlight link was hard to find; concern that a 10k-user cap may be quickly hit.
• Known UX issues on iOS:
  • Hard to dismiss a question; users often resort to force-closing the app.
  • Back navigation relies on iOS edge-swipe gesture, which some users didn’t know.
  • Bug where a quest gets “stuck” after answering; fix is reported but may not be released yet.
• Requested features: native Apple sign-in instead of WebView, easier cancellation of forms, visible indication of one’s own edits on the map, satellite overlay, and hints of nearby recent edits.

Editing workflow, quests, and undo

• There is an in-app undo/history button showing recent edits (time-limited) plus full history on the OSM website.
• Some quests feel underspecified: e.g., sidewalks only on part of a street, or sidewalks on one side.
• On Android there are options like “differs along the way” and per-side sidewalks; on iOS this seems less discoverable or possibly incomplete.
• When options don’t fit reality, users are encouraged to use an “Uh…” / “leave a note” path, but discoverability can be poor.

Comparison with other OSM-based apps

• EveryDoor is preferred by some for POI/store-focused mapping, but others find its icon-heavy UI confusing.
• Go Map!! on iOS offers quests plus full editing power but expects more OSM knowledge.
• OsmAnd, Organic Maps, Cartes, and osmapp.org are recommended for map use and navigation; TomTom praised for combining OSM data with strong traffic info.
• Reminder: OSM is a database; the main site’s map is a demo, not a polished Google Maps replacement.

Kotlin Multiplatform and technical stack

• App uses Kotlin Multiplatform (KMP) and Compose Multiplatform to share almost all code across Android and iOS.
• Maintainers report KMP as relatively stable with minimal “tax” beyond normal Kotlin/Gradle churn; Android framework deprecations are seen as more painful.
• Only a small fraction of the codebase is platform-specific.
• iOS developers must work in Kotlin and Compose, with limited Swift code; Kotlin is considered conceptually close to Swift, and Compose close to SwiftUI.
• Compose Multiplatform is generally liked but has missing features (e.g., scrollbars) and evolving best practices; IDE bugs are a bigger annoyance than KMP itself.
• Some discussion on whether coding agents reduce the benefit of a shared codebase; several argue a single core remains valuable for architecture, tests, and fewer duplicated bugs.

OSM community dynamics and data quality

• One user describes having fun with StreetComplete until edits were reverted by experienced mappers over tagging rules (e.g., whether a highway without sidewalks is “not walkable”).
• Debate centers on:
  • Objective, verifiable tags (legal access, signage) vs subjective “comfort” or safety.
  • Big routing impact of marking ways as non-walkable; many argue this should be reserved for clearly illegal or impossible access.
• A particular “walkability” quest in StreetComplete is acknowledged as controversial and is being removed in a future version due to mismatched wording and tags.
• Others say they feel safer contributing knowing that more experienced editors can revert mistakes, but a reply warns about “deferral of responsibility” and quality risk if people rely too much on reviewers.

Government funding and licensing concerns

• The iOS work was funded by the German federal Prototype Fund and additional support from NLnet; several comments praise German taxpayers for bankrolling globally useful open tools (with solar PV policy cited as another example).
• A separate thread questions OSM’s copyleft-style license, noting incompatibilities with many public-domain/attribution-only datasets and arguing that this hinders data imports; others don’t directly respond within the thread.

OSM as infrastructure and search limitations

• OSM-based apps often prioritize full offline use, which complicates search.
• One commenter notes running a Nominatim instance for a single country requires tens of gigabytes of storage and offers only limited fuzzy search, explaining why many OSM apps have weaker search than Google Maps.