StreetComplete on iOS: Join the Beta Only as a Tester

OpenSourceChoice verdict: join the StreetComplete iOS beta if you can verify every answer on site, review your public OpenStreetMap changes and report beta defects. Do not treat it as a finished App Store release or use it for ambiguous edits. People who need a stable iPhone editor today should evaluate Every Door instead.

This analysis was checked on October 2, 2026. We reviewed the TestFlight announcement, source, release history, current issues, privacy text, license and public discussions. We did not install the beta or make OpenStreetMap edits.

The decision at a glance

Question	Assessment
Current iOS build	TestFlight 64.0.0, equivalent to Android 64.0-alpha2
Stable release	63.4 on Android; there is no stable iOS release yet
Best fit	Careful mappers willing to test a beta in a familiar area and inspect every changeset
Poor fit	iOS 15 users, anyone needing a polished workflow, or people uncomfortable with public edit history
Main risk	A plausible-looking answer creates incorrect map data or exposes a personal location pattern
Real cost	Survey time, verification, bug reporting, battery and data—not a license fee
Alternative to evaluate	Every Door for a stable iOS editor with broader POI-focused editing

Why the iOS beta matters now

StreetComplete entered public TestFlight testing on September 30 after a multi-year migration to Kotlin Multiplatform. The maintainer describes the build as equivalent to the September 28 v64.0-alpha2 Android prerelease and explicitly expects small and large bugs.

Interest is not confined to the announcement. A Hacker News discussion reached 533 points and 135 comments during our check, while a separate r/openstreetmap thread contained active first-use reports and bug discussion. The official OpenStreetMap forum announcement received 52 likes. These are demand signals, not evidence of reliability.

The repository is active: its main branch received fixes on October 2, after the published alpha. Those changes prepare the next build rather than changing the build currently offered through TestFlight.

What StreetComplete does—and does not do

StreetComplete turns nearby OpenStreetMap data gaps into constrained questions such as a road name or a physical feature. Answers are converted into edits and uploaded in meaningful changesets under the user's OpenStreetMap account. The survey workflow can operate offline and is designed to use little data.

That narrow model is the product's advantage. It lowers the tagging knowledge required for observable facts. It does not make an answer correct, moderate it before upload or replace a full geometry and relation editor. Quests are deliberately limited to questions the app can express simply.

The iOS beta also is not at Android feature maturity. The launch announcement lists awkward form dismissal and a map-rendering failure on iOS 15.x. The maintainer says the latter is fixed for the next alpha, but that fix was not yet a published TestFlight build at our cutoff. Current issues also cover onboarding, language and iOS-specific interface behavior.

Who should join—and who should wait

Join if you already understand that OpenStreetMap is a shared public database, can survey a familiar neighborhood and will stop when a question is ambiguous. Beta feedback is useful only when it includes the exact build, device, iOS version and reproducible steps.

Wait if you use iOS 15, need dependable fieldwork, cannot review a changeset, or would be harmed by publishing where and when you map. Do not use the beta to infer access rules, copy another map, or answer from memory. OpenStreetMap's copyright guidance warns contributors not to copy data from sources such as Google Maps without permission.

If you are evaluating the project for an organization, apply an open-source project evaluation checklist before distributing the beta to volunteers. A TestFlight link is not a support or data-governance plan.

Privacy, security and license

StreetComplete's privacy text is unusually direct: OpenStreetMap editing is not anonymous. Each edit, its date and its location is public and attributed to the contributor's account. The app says it does not share the phone's GPS position; it uses location to download nearby data and position the map. It still communicates with OpenStreetMap infrastructure, checks a maintainer-hosted banned-version file and retrieves background tiles from a provider.

The iOS app requests precise foreground location and camera access; the camera is used for photos attached to map notes. Grant only the capabilities needed for the pilot. Avoid photo notes initially, and map an area whose publication does not reveal a sensitive routine.

The code is GPL-3.0-only, while OpenStreetMap data is available under ODbL. There is no software license fee. Modified redistribution still carries GPL obligations, and contributed map facts must respect the database's sourcing rules.

We found no repository security policy and no published GitHub security advisory at the cutoff. That absence is not proof of safety. TestFlight provides a controlled Apple beta channel, but it does not validate edit quality, privacy choices or every defect. The central pilot risk is corrupted shared data and an attributable movement pattern, not merely an app crash.

The real operational cost

The download is free; responsible use is not. A tester needs a compatible iPhone, an Apple TestFlight flow, an OpenStreetMap account and time outdoors. Add time to inspect uploaded changes, respond to other mappers and file useful defects. Location, background tiles and synchronization also consume battery and data.

Treat incorrect edits as incidents. Record the changeset, correct or revert the problem promptly and explain it when another mapper asks. The F-Droid 2.0 rollout checklist uses the same principle: a new mobile build deserves a constrained pilot before broad adoption.

Compare Every Door

Every Door is the practical alternative to test when you need a stable iOS app now. It is available through the App Store and focuses on editing shops, amenities, entrances and other points of interest. Its manual modes provide more freedom than StreetComplete's quest flow, which also means a steeper responsibility for choosing correct tags.

The products are not substitutes in every workflow. Prefer StreetComplete for guided, observable questions; prefer Every Door when the job requires deliberate POI collection or editing not exposed as a quest. Teams doing complex geometry or relation work should evaluate a full editor separately.

A measurable 20-edit pilot

Install only from the official TestFlight link. Record the StreetComplete build, iPhone model and iOS version.
Use a familiar three-block area with no sensitive home, work or school routine. Review OpenStreetMap's contributor and copyright rules first.
Choose 20 low-ambiguity quests answerable by direct observation. Skip access, legal or temporal questions you cannot prove.
Avoid map-note photos during the first pilot. Before upload, re-read every answer and reject anything inferred from another map.
Open the resulting changeset on openstreetmap.org within 24 hours. Confirm all 20 edits landed on the intended objects and review any community comment.
Log crashes, failed rendering, confusing forms, duplicate questions, sync failures and material battery drain. Report reproducible beta defects through the project's requested channel.
Pass only with zero unexplained or disputed edits, zero data loss, successful synchronization and no blocker across two sessions. Otherwise correct the map, stop the pilot and wait for the next build.

Conclusion

StreetComplete's iOS beta opens a valuable guided-mapping workflow to iPhone users, but its public database writes make “beta” more consequential than a cosmetic glitch. Join as a tester, not as a passive early adopter.

Use direct observation, inspect the changeset and require a clean 20-edit pilot. If you need a mature iOS editor or broader POI controls today, evaluate Every Door while StreetComplete's TestFlight release settles.