Prerequisites
Basic computer literacy and a willingness to document experiments.
Learning objectives
- Explain the stage-specific model and its limits
- Apply the listed concepts using a controlled exercise
- Record results, failure cases and a reproducible evidence trail
Topics to learn
- Application lifecycle and process model
- Project structure and build variants
- Permissions and platform APIs
- Emulator/device debugging
- SwiftUI specialization: Track-specific focus: SwiftUI. Use the tools and standards named in this path; avoid treating this route as a generic overview of Mobile Development.
Tools
Android Studio or XcodePlatform SDKGit
Hands-on exercise
Build a minimal app and document lifecycle callbacks across rotation/background/restore. Context for this route: Track-specific focus: SwiftUI. Use the tools and standards named in this path; avoid treating this route as a generic overview of Mobile Development.
Suggested project
A multi-screen starter app with reproducible build instructions. The outcome must directly demonstrate SwiftUI, not merely list tools.
Learning resources
Completion criteria
The app handles lifecycle transitions and permissions predictably. Evidence must be reproducible and tied to SwiftUI.
Next: Native language & platform APIs
Prerequisites
Completion of the previous stage and a working local practice environment.
Learning objectives
- Explain the stage-specific model and its limits
- Apply the listed concepts using a controlled exercise
- Record results, failure cases and a reproducible evidence trail
Topics to learn
- Language type system and concurrency
- UI and navigation primitives
- Device capabilities and permissions
- Platform resource management
- SwiftUI specialization: Track-specific focus: SwiftUI. Use the tools and standards named in this path; avoid treating this route as a generic overview of Mobile Development.
Tools
Kotlin/Swift/Flutter SDKPlatform documentationDebugger
Hands-on exercise
Implement one device capability behind a permission-aware interface. Context for this route: Track-specific focus: SwiftUI. Use the tools and standards named in this path; avoid treating this route as a generic overview of Mobile Development.
Suggested project
A small app feature using a native API with graceful denial handling. The outcome must directly demonstrate SwiftUI, not merely list tools.
Learning resources
Completion criteria
Permission denial and lifecycle changes do not crash or expose data. Evidence must be reproducible and tied to SwiftUI.
Next: UI composition & adaptive layouts
Prerequisites
Completion of the previous stage and a working local practice environment.
Learning objectives
- Explain the stage-specific model and its limits
- Apply the listed concepts using a controlled exercise
- Record results, failure cases and a reproducible evidence trail
Topics to learn
- Declarative or view-based UI composition
- Navigation and deep links
- State ownership and rendering
- Dynamic type and accessibility
- SwiftUI specialization: Track-specific focus: SwiftUI. Use the tools and standards named in this path; avoid treating this route as a generic overview of Mobile Development.
Tools
Compose/SwiftUI/Flutter widgetsUI inspectorDesign system tokens
Hands-on exercise
Create a list/detail flow with loading, empty, error and offline states. Context for this route: Track-specific focus: SwiftUI. Use the tools and standards named in this path; avoid treating this route as a generic overview of Mobile Development.
Suggested project
An adaptive mobile interface with reusable components. The outcome must directly demonstrate SwiftUI, not merely list tools.
Learning resources
Completion criteria
The UI works across supported screen sizes and accessibility settings. Evidence must be reproducible and tied to SwiftUI.
Next: Networking, data & offline-first design
Prerequisites
Completion of the previous stage and a working local practice environment.
Learning objectives
- Explain the stage-specific model and its limits
- Apply the listed concepts using a controlled exercise
- Record results, failure cases and a reproducible evidence trail
Topics to learn
- HTTP client and serialization
- Local database and migrations
- Caching and offline state
- Retry and conflict policies
- SwiftUI specialization: Track-specific focus: SwiftUI. Use the tools and standards named in this path; avoid treating this route as a generic overview of Mobile Development.
Tools
Room/Core Data/SQLiteHTTP clientMock API
Hands-on exercise
Implement a repository that falls back to cached data and reports sync state. Context for this route: Track-specific focus: SwiftUI. Use the tools and standards named in this path; avoid treating this route as a generic overview of Mobile Development.
Suggested project
An offline-capable feature with migration tests. The outcome must directly demonstrate SwiftUI, not merely list tools.
Learning resources
Completion criteria
Data survives restart and sync failures are visible and recoverable. Evidence must be reproducible and tied to SwiftUI.
Next: Architecture, concurrency & background work
Prerequisites
Completion of the previous stage and a working local practice environment.
Learning objectives
- Explain the stage-specific model and its limits
- Apply the listed concepts using a controlled exercise
- Record results, failure cases and a reproducible evidence trail
Topics to learn
- MVVM or platform-appropriate architecture
- Async tasks, coroutines or structured concurrency
- Background scheduling
- Dependency injection
- SwiftUI specialization: Track-specific focus: SwiftUI. Use the tools and standards named in this path; avoid treating this route as a generic overview of Mobile Development.
Tools
ViewModel or equivalentWorkManager/background tasksDI tool
Hands-on exercise
Move business logic from the screen into a testable use case and simulate cancellation. Context for this route: Track-specific focus: SwiftUI. Use the tools and standards named in this path; avoid treating this route as a generic overview of Mobile Development.
Suggested project
A feature module with deterministic state and injectable dependencies. The outcome must directly demonstrate SwiftUI, not merely list tools.
Learning resources
Completion criteria
Concurrency is lifecycle-aware and the core logic is independently tested. Evidence must be reproducible and tied to SwiftUI.
Next: Quality, security & performance
Prerequisites
Completion of the previous stage and a working local practice environment.
Learning objectives
- Explain the stage-specific model and its limits
- Apply the listed concepts using a controlled exercise
- Record results, failure cases and a reproducible evidence trail
Topics to learn
- Unit/UI/integration testing
- Secure storage and transport
- Crash, memory and battery profiling
- Accessibility and privacy review
- SwiftUI specialization: Track-specific focus: SwiftUI. Use the tools and standards named in this path; avoid treating this route as a generic overview of Mobile Development.
Tools
Platform test runnerProfilerOWASP MASVS where relevant
Hands-on exercise
Profile a screen, threat-model its data and add a regression test. Context for this route: Track-specific focus: SwiftUI. Use the tools and standards named in this path; avoid treating this route as a generic overview of Mobile Development.
Suggested project
A device QA report with measurements and security decisions. The outcome must directly demonstrate SwiftUI, not merely list tools.
Learning resources
Completion criteria
Performance and security improvements are measurable and documented. Evidence must be reproducible and tied to SwiftUI.
Next: Release engineering & store readiness
Prerequisites
Completion of the previous stage and a working local practice environment.
Learning objectives
- Explain the stage-specific model and its limits
- Apply the listed concepts using a controlled exercise
- Record results, failure cases and a reproducible evidence trail
Topics to learn
- Signing and provisioning
- Build variants and release configuration
- Crash reporting and staged rollout
- Store policy and privacy disclosures
- SwiftUI specialization: Track-specific focus: SwiftUI. Use the tools and standards named in this path; avoid treating this route as a generic overview of Mobile Development.
Tools
Gradle or Xcode build toolsCI workflowRelease checklist
Hands-on exercise
Create a signed test build and verify installation/update behaviour. Context for this route: Track-specific focus: SwiftUI. Use the tools and standards named in this path; avoid treating this route as a generic overview of Mobile Development.
Suggested project
A release candidate with version notes, privacy summary and rollback plan. The outcome must directly demonstrate SwiftUI, not merely list tools.
Learning resources
Completion criteria
The app builds repeatably and secrets/signing material are handled safely. Evidence must be reproducible and tied to SwiftUI.
Next: Capstone: production mobile app
Prerequisites
Completion of the previous stage and a working local practice environment.
Learning objectives
- Explain the stage-specific model and its limits
- Apply the listed concepts using a controlled exercise
- Record results, failure cases and a reproducible evidence trail
Topics to learn
- Product scope and user journeys
- Architecture and offline behaviour
- Automated tests and device QA
- Demo, portfolio and maintenance plan
- SwiftUI specialization: Track-specific focus: SwiftUI. Use the tools and standards named in this path; avoid treating this route as a generic overview of Mobile Development.
Tools
Platform SDKIssue trackerCI and test devices
Hands-on exercise
Complete a real user journey under slow network, denied permission and interrupted lifecycle conditions. Context for this route: Track-specific focus: SwiftUI. Use the tools and standards named in this path; avoid treating this route as a generic overview of Mobile Development.
Suggested project
A polished app with source, demo build, tests and technical case study. The outcome must directly demonstrate SwiftUI, not merely list tools.
Learning resources
Completion criteria
The app is reproducible, tested and demonstrates platform-specific judgement. Evidence must be reproducible and tied to SwiftUI.
End of roadmap: Complete the final project and build your portfolio.