If your code looks like it's Kotlin & quacks like it's Kotlin, then it probably is Swift.
summary
Built a tiny dog‑breed guessing game with 10 rounds and local scoring, implemented natively on both platforms while swapping roles so iOS dev writes Kotlin and Android dev writes Swift. Architecture uses MVVM, Retrofit/Alamofire for networking, SharedPreferences/UserDefaults for storage, and shares around 80% of repository code and ~50% of ViewModel logic. Kotlin coroutines, LiveData and Koin simplify Android async and DI; Swift uses structs, protocols and enums (sealed classes emulate payload enums). The experiment succeeds and reveals concrete syntax and platform tradeoffs.
AI-written summary · about
chapters (6)
- 0:00Introduction and motivation
- 6:38Experiment design and app concept
- 14:10Language similarities between Kotlin and Swift
- 20:52Key differences in Kotlin and Swift
- 27:38Kotlin-specific features and tools
- 33:27Memory management and final thoughts
related talks
42mIf your code looks like it's Kotlin & quacks like it's Kotlin, then it probably is Swift.
22mIf your code looks like it’s Kotlin & quacks like ...
28mKotlin for Swift Developers
39mAnd That, Folks, is How We Shared Code Between Android, iOS and the Backend
48mKotlin for Android, iOS & the mobile web
25mKotlin Multiplatform Mobile in production: key takeaways from developing two cross-platform apps
37mGoing Native
52miOS Architecture with Multiplatform
