0 of 4 done
“How this stack does it.” Sections 01–14 hold true whichever you pick; this folder is the per-stack implementation layer, copying the backend/frameworks convention.
Read note 14 first — it’s the decision these folders implement.
| Stack | Language | Best for |
|---|---|---|
| ios/ | Swift | Platform-idiomatic iOS, deep OS integration |
| android/ | Kotlin | Platform-idiomatic Android, the larger global market |
| flutter/ | Dart | Design-led apps, one codebase, consistent UI |
| react-native/ | TypeScript | Teams that already know React |
Kotlin Multiplatform doesn’t get its own folder because it isn’t a UI framework — it’s shared Kotlin logic under native SwiftUI and Compose UIs. It’s covered in note 14 and the Kotlin course.
Related
- the mobile course · projects
- backend/frameworks — the convention this copies
- languages — the languages themselves
Jump to a subject
Software engineering
Infrastructure & security
Computer science
Hardware & engineering