If your code looks like it’s Kotlin & quacks like ...
summary
Claims that learning Kotlin and Swift makes cross‑platform fluency practical get tested by implementing a small dogs app on both Android and iOS using the dog API; bottom layers share a deliberately similar design while UI layers stay platform specific. The build uses clean architecture with MVVM, Android picks up Koin for DI, and data mapping/generics translate nearly identically. The experiment runs successfully and surfaces concrete differences in enums, protocols/interfaces and value vs reference semantics.
AI-written summary · about
chapters (14)
- 0:00Start
- 4:21DESIGNING AN EXPERIMENT
- 7:17DECIDING THE ARCHITECTURE
- 8:51Higher Order Functions
- 9:21TYPE CASTING
- 9:43GENERICS
- 12:04ENUMS
- 13:02SEALED CLASSES
- 13:41STRUCTS
- 14:28DATA CLASSES
- 15:06PROTOCOLS
- 17:20COROUTINES
- 18:33WHAT DID WE LEARN?
- 20:32GOING FURTHER
related talks
41mIf your code looks like it's Kotlin & quacks like it's Kotlin, then it probably is Swift.
42mIf your code looks like it's Kotlin & quacks like it's Kotlin, then it probably is Swift.
22mArchitecting a Kotlin Multiplatform App
48mEffective Multiplatform Kotlin Development
34mCode Sharing is caring - Cross-Plattform Development
45mSDK Design and Publishing For Kotlin Multiplatform Mobile
28mKotlin for Swift Developers
52miOS Architecture with Multiplatform