StreetComplete, the popular open-source Android app that turns OpenStreetMap editing into a casual quiz-like experience, is attempting something architecturally ambitious: porting to iOS without forking into a second codebase. The project's approach — Kotlin Multiplatform plus Compose Multiplatform — is a bet that the toolchain is mature enough to support a production mobile app on Apple hardware while keeping maintenance overhead close to zero. The technical strategy is clear-eyed. The app is written in 100% Kotlin. Rather than rewrite in Dart (Flutter) or maintain parallel Swift code, the team is transpiling Kotlin to native iOS code and rebuilding the UI layer in Compose Multiplatform, currently in beta for iOS. The migration requires separating all platform-specific code from application logic, replacing Android/Java dependencies with Kotlin multiplatform equivalents, and incrementally converting Android XML layouts to Jetpack Compose before the final hop to Compose Multiplatform. The project board uses a Kanban-style task tracker, and lead developer estimates suggest roughly one person-year of total effort. As of mid-2024, the migration was approximately 50% complete after the lead worked on it full-time for the first half of the year. The remaining scope is explicitly framed as too large for a solo developer — the project depends on community contributions to finish. This is a genuinely generative open-source play. StreetComplete contributes to OpenStreetMap, a global public commons. An iOS port doubles the potential contributor base for both the app and the underlying map data. No venture capital, no subscription model, no data harvesting — just a public good expanding its reach. The project accepts sponsorships to fund developer time but has no extractive business model. The risk is real. Compose Multiplatform for iOS is beta software. Betting a year-plus of community labor on a framework that could stall, break, or diverge from Jetpack Compose is a nontrivial wager. If JetBrains deprioritizes iOS support or the API surface fractures, the migration work could become stranded. The project is structurally dependent on a single corporate backer's framework roadmap. The community model is the load-bearing element. The project explicitly invites contributors to claim tasks, learn Compose, help with issue triage, or provide financial sponsorship. The SotM Europe 2024 talk slides (with speaker notes) serve as onboarding documentation. This is how healthy open-source projects scale — by making the work legible and the entry points clear. If this succeeds, it becomes a reference implementation for Kotlin Multiplatform mobile apps in the open-source world, proving the stack can support real production software beyond corporate pilot projects. If it stalls at 50%, it becomes another cautionary tale about cross-platform promises outrunning cross-platform reality.
