Phase 3Days 12-16

Expo Router & Application Architecture

File-based routing, stacks, tabs, deep links, auth gates, and scalable feature boundaries

Phase Goal

Design navigation that survives growth and makes every screen deep-linkable and testable.

Progress

Day 12: Expo Router Mental Model

Day 13: Dynamic Routes, Parameters & Deep Links

Day 14: Tabs, Nested Layouts & Modal Flows

Day 15: Authentication Gates & Feature Architecture

Day 16: Mini Project — Local League Matchday

Capstone
Local League Matchday

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.

  • Typed fixture, club, and venue routes with identifier-only parameters
  • Nested tabs and stacks plus a result-report modal with correct back behavior
  • Cold/warm deep-link, browser-back, Android-back, invalid-ID, and auth-restore evidence
  • Transfer: add a postponed-fixture route reached from both a notification-shaped URL and the schedule

Phase Complete!

After this phase, you'll be able to:

  • src/app routes, URLs, index, and root layout
  • Stack navigation, Link, router actions, and headers
  • Route groups versus URL segments
  • Typed routes and route ownership
  • Dynamic segments and local/global search params
  • Serializing route identity rather than whole objects
  • Universal links, app schemes, and cold-start routing
  • Not-found, invalid IDs, and recovery paths

You can apply Phase 3 skills in a tested mobile project on Android and iOS.