Phase 10Days 53-57

Final Capstone — Lantern Live Festival Companion

Offline-first festival planning with schedules, venue maps, personal media, organizer updates, secure roles, widgets, and production delivery

Phase Goal

Integrate the entire course into a deployed attendee-and-organizer product that proves offline correctness, inclusive navigation, device capability, native extensions, performance, and safe operation.

Progress

Day 53: Festival Product Architecture & Evidence Plan

Day 54: Schedule, Venue Maps & Offline Itineraries

Day 55: Personal Memories, Live Changes & Native Surfaces

Day 56: Quality, Inclusion, Security & Performance Proof

Day 57: Final Project — Ship Lantern Live

Capstone
Lantern Live Festival Companion — SHIPPED

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.

  • Correctness: a saved itinerary survives restart and offline use, duplicate mutations are harmless, and a changed or cancelled session reconciles visibly
  • Capability: typed routing, scalable programme UI, maps with manual fallback, optional camera, notifications, secure organizer role, custom native surface, and denial recovery
  • Evidence: layered tests, assistive-technology task audit, release traces, signed builds, symbolicated failure, update compatibility, rollback, dashboards, and runbooks
  • Transfer: add an emergency venue-closure requirement that reroutes affected plans without overwriting attendee choices

Phase Complete!

After this phase, you'll be able to:

  • Attendee, accessibility steward, and organizer decisions, scope, non-goals, and measurable success
  • Performance, venue, session, itinerary, announcement, memory, and sync domain models
  • Typed route map, Redux and cache boundaries, API contracts, widget data, and offline invariants
  • Threat model, permission minimization, test strategy, operational budgets, and architecture decisions
  • Deep-linkable programme, performer, venue, and saved-itinerary flows
  • Venue map, optional foreground location, manual wayfinding, and accessibility filters
  • Offline schedule cache, idempotent itinerary queue, organizer conflicts, and deterministic merge rules
  • Freshness timestamps, cancellation visibility, sync status, and no-location/no-network UX

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