Why SwiftUI?
summary
Claim: SwiftUI makes UI code declarative and reduces glue work by replacing storyboards and segues with real Swift components and live Xcode previews, and it expects data flow via Combine rather than imperative callbacks. Demonstrations show using @State, @Binding and @EnvironmentObject with the $ prefix, composing layouts with VStack/HStack, navigating with NavigationLink, and wiring publishers and subjects (passThrough / CurrentValueSubject) into Observable objects. Targets require iOS 13 macOS 10.15 watchOS 6 and it's sold as faster prototyping—five day sprints to working apps.
AI-written summary · about
chapters (54)
- 0:00Introduction
- 2:53Why
- 3:26Clan Compiler
- 3:47Objective C
- 4:27Declarative Programming
- 5:11UI Documentation
- 5:34Apple History
- 5:51Android History
- 6:03Jetpack Compose
- 6:42Android Team
- 6:52Speed of Thought
- 7:03Tools
- 7:38Learning
- 8:51SwiftUI
- 12:29Growing pains
- 12:59Benefits of SwiftUI
- 14:24SwiftUI Architecture
- 15:00SwiftUI Canvas
- 15:36Live Preview
- 16:35View
- 17:08Stacks
- 18:00Forms
- 18:26Custom Views
- 18:52SF Symbols
- 19:15Reusable Components
- 20:03No More Control
- 20:13Navigation
- 21:40Logic
- 22:08Navigation button
- 23:02Animation
- 23:28Swift UI
- 25:55ModelViewModel
- 26:11State Layer Management
- 27:09Key Points
- 29:15AtState
- 29:50Atbinding
- 30:57Appbinding
- 31:26Binding
- 32:36Combine Framework
- 33:53Publishers and Subscribers
- 34:06Combined Framework
- 35:19FlatMap
- 37:13Combine
- 38:31The User Community
- 38:41Rules for subscribing
- 39:05Sign and Sink
- 40:04Notification Center
- 40:52Subject
- 42:29External Data
- 43:11Object Binding
- 45:00Important Notes
- 45:28Environment Object
- 47:34React Native
- 48:18Conclusion
