If your code looks like it's Kotlin & quacks like it's Kotlin, then it probably is Swift.
summary
Claim: Kotlin and Swift are similar enough to make a small native team bilingual across Android and iOS. Built a simple dog-guessing app using the Dog API, Retrofit (Android) and Alamofire (iOS), Kotlin coroutines + LiveData, Koin for DI, and SharedPreferences/UserDefaults for scores; Swift uses structs/enums, Kotlin uses data classes/sealed classes. Result: data/repo layers reach ~80% similarity, view models ~50%, UI is platform-specific, and the experiment works.
AI-written summary · about
chapters (7)
- 0:00Introduction and motivation
- 6:28Experiment setup and goals
- 14:55Language similarities between Kotlin and Swift
- 22:38Key differences in enums and structs
- 27:55Protocols, coroutines, and memory management
- 35:07Lessons learned and bilingual benefits
- 41:32Q&A and closing remarks
related talks
41mIf 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
38mKotlin & Swift: Convergent Evolution?
49mEffective Kotlin-Swift Interoperability
39mAnd That, Folks, is How We Shared Code Between Android, iOS and the Backend
43mDoppl Code Sharing
21mKotlin For Swift Developers
