roadmap
- 01
- 02
- 03
- 04
- 05
- 06
- 07
- 08
Prepare for SwiftUI interviews on how views, state and data flow drive an Apple platform app. Covers the Swift language beneath it, persistence and charts, testing and packages.
548 of 548 questions in your plan: 0 known, 0 in progress, 0 due, 0 skipped, 548 new. 0 cut, outside your plan.
SwiftUI gets its own conversation in most iOS loops, after a coding task and before, from middle level up, a feature design discussion. The questions usually start from a screen that behaves wrongly. A view model created inline under @ObservedObject is rebuilt every time its parent redraws. A row keeps a stale price because the == behind .equatable() ignores the field that changed. A feed jumps when newer posts are inserted above the one being read. A SwiftData edit survives the Cancel button because the main context had already saved it.
Naming the wrapper or modifier that fixes the screen is where an answer starts; what lifts it is the mechanism underneath. That means the identity SwiftUI gives each view and the moment it decides a view is new, the property reads Observation records while body runs, the actor a model object belongs to and why it cannot simply be handed to another, and what an availability check costs when the deployment target is older than the API the design wants.
Swift itself opens the plan because many SwiftUI follow-ups turn into language questions. Value and reference types explain why a view is cheap to recreate and a model is not, and concurrency explains why a view model usually lives on the main actor. SwiftUI follows, beginning with views and composition and state and data flow, where ownership and identity are settled before the parts of the framework that build on them.
Next come the frameworks a SwiftUI app reaches for, each placed after the part of SwiftUI it plugs into. SwiftData needs state and data flow first, since @Query and the model context arrive through the view tree, and its schema migrations are where its senior questions go. A chart in Swift Charts is itself a SwiftUI view, so it asks for little more than the framework above it.
The plan ends with the app around the views. Bridging to UIKit is the seam a team with an older codebase works on every day: hosting controllers one way, representables the other. Swift Testing checks the logic you moved out of body, and the package manager closes on how that code is split into modules, pinned and built.
Someone new to Apple platforms gets the most from the top of the plan: optionals, value types and closures first, then views and state, because the later modules assume that model. An engineer who already ships SwiftUI loses little by beginning at the UI module and treating the language as the place to go back to when a SwiftUI answer runs into a copy, a capture or an actor. With study order switched to by topics, the page then follows the plan in the sequence above, which keeps SwiftData next to the state questions it depends on. The plan stays inside the app's UI and the code around it. Networking layers, push notifications, background refresh and shipping through the App Store are part of the job but not of this plan; the [iOS Developer roadmap](/roadmaps/ios) puts SwiftUI among the platform questions that role also gets.
Someone new to Apple platforms gets the most from the top of the plan: optionals, value types and closures first, then views and state, because the later modules assume that model. An engineer who already ships SwiftUI loses little by beginning at the UI module and treating the language as the place to go back to when a SwiftUI answer runs into a copy, a capture or an actor. With study order switched to by topics, the page then follows the plan in the sequence above, which keeps SwiftData next to the state questions it depends on.
The plan stays inside the app's UI and the code around it. Networking layers, push notifications, background refresh and shipping through the App Store are part of the job but not of this plan; the iOS Developer roadmap puts SwiftUI among the platform questions that role also gets.