StreetComplete on iOS is now in public beta
- ID
- 30837
- Status
- summarized
- Published
- 01 Oct 2026, 6:59 PM
- Fetched
- 02 Oct 2026, 12:26 AM
- Provider
- Hacker News
- Category
- dev-community
- Original URL
- https://github.com/streetcomplete/StreetComplete/issues/5421
- Source URL
- https://hnrss.org/best
Summary
- Score
- 6.0
- Created
- 02 Oct 2026, 12:27 AM
- Tags
- Audience
- developersvibe_coders
What happened
StreetComplete's long-running iOS tracking issue (#5421, opened Dec 20, 2023) has reached 11/11 completed tasks and is now in public beta on iOS. The port keeps the app's 100% Kotlin codebase and uses Kotlin Multiplatform with Compose Multiplatform for the UI, rather than rewriting everything in Dart as Flutter would require (the approach Every Door took). The plan explicitly includes incrementally migrating the existing Android XML layouts to Jetpack Compose and separating platform-specific code from application logic; the repo has 4.9k stars and 457 forks, and the HN thread drew 309 points and 63 comments.
Why it matters
If you maintain a Kotlin Android app and have deferred iOS, this is a concrete worked example of the KMP path: one codebase retained, but the entire UI still has to be re-created in Compose Multiplatform — so the real cost is a UI migration, not a free second platform. The decision point it sharpens is KMP vs Flutter: StreetComplete chose KMP specifically to avoid rewriting its Kotlin logic in Dart. There is no Malaysian or SEA angle in this text; the impact is limited to teams doing cross-platform mobile work.
Discussion angle
For your next app, would you pick Kotlin Multiplatform or Flutter — and does StreetComplete's trade-off (keep Kotlin logic, rewrite the whole UI in Compose) actually beat Flutter's rewrite-everything-in-Dart once you count maintenance over 2-3 years?