One mobile product closes every phase. Each project proves a different hiring signal: navigation, offline correctness, device APIs, performance, native code, or production delivery.
Phase 1 · Mobile Foundations & Modern Expo
Build an offline board for a housemate deciding which plants need attention today. It must distinguish due, completed, skipped, and undone care without timers, accounts, notifications, or a backend.
Phase 2 · Layout, Styling & Responsive Mobile UI
Build a responsive recipe catalogue for a neighborhood cooking club deciding what to cook with available time and dietary constraints. The supplied local dataset must remain usable at large text sizes and on narrow phones and tablets.
Phase 3 · Expo Router & Application Architecture
Build a universal matchday guide for supporters choosing a fixture, venue, and followed club. A shared fixture URL must open correctly from a cold start, survive signed-out and expired-session states, and recover from an unknown fixture.
Phase 4 · Data, Redux & Offline-First State
Build an offline-first ledger for volunteers deciding how limited pantry stock should be reserved across household requests. Local drafts and reservations must survive restarts, duplicate retries must not double-decrement stock, and competing edits must produce a visible reconciliation choice.
Phase 5 · Device Capabilities & Native Product Features
Build a self-guided tree walk for families choosing nearby stops and recording private observations. The walk must remain useful when camera, precise location, or notifications are denied and must never imply that an observation was uploaded to a public service.
Phase 6 · Motion, Gestures, Performance & Accessibility
Build a rehearsal tool for a dance leader arranging hundreds of lighting and movement cues. Drag and pinch interactions may accelerate editing, but every decision must also be possible with labelled controls, switch access, keyboard input where available, and reduced motion.
Phase 7 · Testing, Debugging & Mobile Security
Build a staff-facing consent-status app that answers only whether a participant may join a selected activity. Store the minimum metadata, gate staff access with platform authentication, redact sensitive screens when backgrounded, and state clearly what a rooted or jailbroken device can still expose.
Phase 8 · Native Toolchains, Widgets & Custom Capabilities
Create a privacy-preserving study-space app that classifies short on-device ambient samples into quiet, moderate, or loud bands without recording or retaining audio. Matching Android and iOS widgets show the last completed sampling window and its age.
Phase 9 · Production Delivery & Operations
Take a supplied local cinema programme app from reproducible build profiles to a review-ready release. Prove that a schedule-text update can roll forward and back safely, while a native notification capability change is held for a new binary.
Phase 10 · Final Capstone — Lantern Live Festival Companion
Build and distribute an offline-first festival companion in which attendees compose accessible itineraries, navigate venues, receive schedule changes, keep optional private photo memories, and view the next saved session on a native surface while authorized organizers publish bounded updates.