When You Can’t Go All In On SwiftUI, Build a Hybrid UI App Instead!
summary
Claims that an app can be migrated incrementally by mixing frameworks and demonstrates four concrete use cases with a working tip calculator as the example, swapping a UIKit segmented control for a SwiftUI Picker and adding a payment screen both directions. Implements UIViewRepresentable and Coordinator to wrap UIViews, UIHostingController and ObservableObject to host SwiftUI screens, uses @Binding and @Published to sync state, and shows demos that work end to end.
AI-written summary · about
chapters (9)
- 0:00Start
- 9:06Takeaway Point
- 16:12SwiftUI App- Add UIKit component
- 18:52Recap: SwiftUl app- Add UIKit component
- 25:01Case 2 Recap: SwiftUI app- Add UIKit Screen
- 33:25Recap: UIKit app- Add SwiftUI screen
- 34:10Resources
- 35:26Questions?
- 36:43Case 2: SwiftUI app- Add UIKit screen
related talks
37mAdopting SwiftUI at scale
46mScaling Up With SwiftUI: Migrating iOS Apps To SwiftUI
40mFunctional iOS Architecture in the SwiftUI Era
23mUsing SwiftUI as a Language
34mBuilding Shared UIs Across Platforms With Compose
26mThe SwiftUI Mindset: 5 Key Ideas to Avoid Common Pitfalls
17mMastering SwiftUI Previews: How the Project Structure can hel
28mFlexible View Controller Interfaces With Swift 4