Jetpack Compose vs SwiftUI
summary
Builds a small image app with a grid, search and a detail view with a favorite toggle and shows both frameworks actually working. On Compose uses MVVM with immutable StateFlow bridged via collectAsState, a LazyVerticalGrid, Coil’s rememberImagePainter, side effects via launchEffect, eager updates with mutableStateOf and route‑based navHost navigation. On SwiftUI uses ObservableObject with @Published, async/await tasks, @StateObject and two‑way binding with $, built‑in searchable and LazyVGrid and NavigationLink. Navigation and Xcode previews feel easier, Compose requires emulator for full navigation testing.
AI-written summary · about
chapters (14)
- 0:00Introduction
- 1:17Overview
- 2:40Compose
- 8:56Search
- 15:09UI State
- 15:32Like Image
- 18:46Navigation
- 20:28SwiftUI
- 22:57Bridge to Repository
- 25:14Lazy Grid
- 26:31Searching
- 29:02Toggle
- 30:55Nav
- 32:49Conclusion
related talks
26mJetpack Compose and SwiftUI: A side-by-side comparison
40mSwiftUI vs Jetpack Compose by an Android Engineer
34mBuilding Shared UIs Across Platforms With Compose
45mCompose vs SwiftUI: Spot 10 Differences
40mBuilding Multiplatform Apps with Compose
19mUsing Jetpack libraries in Compose
41mJetpack Compose is Swift (UI).
01h 16mA Composable New World!