let swift == val kotlin - Why iOS is so important for Android, and vice versa
summary
A simple La La Land app is built: two screens (cast grid and songs list), a detail view with lyrics and a toggleable favorite, wired via storyboards, segues and a navigation controller so the back button works automatically. Code examples use Swift types, IBOutlets/IBActions, UIViewController lifecycle methods, URLSession + JSONSerialization for REST (no Retrofit equivalent), and SQLDelight / Core Data options for persistence. The claim is that layering business logic lets teams reuse architecture across platforms and that Kotlin/Native makes sharing this logic practical. UICollectionView = RecyclerView IBOutlets/IBActions ≈ view binding SQLDelight supports shared persistence
AI-written summary · about
chapters (6)
- 0:00Introduction and imposter syndrome
- 8:18iOS tools and Swift basics
- 15:48Building the first screen
- 25:16Second screen and navigation
- 32:01Networking and persistence
- 37:19Learning resources and closing
related talks
25mThe ever increasing convergence of native Android and iOS development
26mThe ever increasing convergence of native iOS and Android mobile development
28mThe ever increasing convergence of native iOS and Android mobile development
25mUnderstanding native iOS from an Android perspective
26mI Walk The Line
44mAn iOS Developer's Guide to Building Android Apps
39mI’m an iOS Engineer, So I Can Build Android Apps Too…
36mBest Practices for Developing Amazing Kotlin Multiplatform Apps