Problem
Flight tracking depends on live data shape, routing, search, and map context.
Work
W06
Next Flights
A flight tracking app with search, maps, CMS-backed content, and typed application structure.
Story
Next Flights combines search, maps, boards, and typed routes.
Constraint
The public page can show owned artwork and repo evidence but not live service credentials.
Approach
Use product artwork to show the visual direction. Describe the typed application structure without exposing secrets. Treat the case as product anatomy: artwork, routes, search, and map context.
Outcome
The case shows a product structure built around search, maps, and route boundaries.
Evidence
Owned artwork and repo structure show search, map, board, and API boundaries without exposing live tokens.
Problem
Problem
Flight tracking depends on live data shape, routing, search, and map context.
Product anatomy / Owned captureApproach
Approach
Use product artwork to show the visual direction. Describe the typed application structure without exposing secrets. Treat the case as product anatomy: artwork, routes, search, and map context.
Product anatomy / Owned capture
Constraint
Constraint
The public page can show owned artwork and repo evidence but not live service credentials.
Interface artwork / Owned captureOutcome
What changed
Next Flights shows app structure, search, maps, and owned product artwork.
Interface artwork / Owned captureResult
What changed
- Next Flights shows app structure, search, maps, and owned product artwork.
Claims
Public claims kept inside the available evidence.
- README lists real-time tracking, search, maps, and CMS
- Owned product artwork
- Typed Next.js application structure