GDC Demo — Engineering Proposal
Target for GDC
A guided loop through the same screens, in a new order. No matchmaking, no menus, return to start after Demo finishes, low cognitive overhead for Player.
Step 1Generate your creature
↺ Repeat × 3 Battles
New Cards
3 generated for you
Pick again
→ back to battle
New cards, repeat
EndExplore freely, restart
Order of Operations by Team
Burndown to Get There
Three parallel tracks. Scoping comes before work, we can't prioritize what we haven't identified!
UI
Mollie
1 — Critical First
Scope What's Broken
- Paul: Render every demo screen at iPad Mini resolution
- Mollie: highlight every artifact
- Ranked problem list before any fixes start
2 — Feed to Josh
Scope Missing Screens
- Identify missing or broken Figma components
- Hand clear list to Josh — unblocked tasks
Eng
Paul + JP
1 — Do Now
Merge BB2 → Main
- Hotfixes from main → multiplayer branch
- Multiplayer branch → main
- Test iPad ↔ iPhone on device
2 — Build
Wire the Demo Loop
- New flow controller: create → pick cards → battle → repeat × 3 → inventory
- Skip matchmaking, deck builder, lobby
- Auto-advance transitions, loopback after 3 battles
3 — Go/No-Go by EOW
On-Device Image Gen Benchmark
- Get distilled/one-step model onto device
- Benchmark on Mollie's iPad + Paul's
- Decision: Cloud vs Local GDC
Design
JP — gap audit
1 — Audit First
What's Missing from Eng?
- Review BB2 screens against current design spec
- Flag every design element with no eng implementation
- Traits, arena cards, anything else unbuilt
- Scope gap list
2 — Decisions Needed
Open Questions
- Are traits in for GDC?
- Arena card passive trigger — UX needs resolve
- Show card names in demo or keep opaque?
Constraint
No New Design Work
- Polish what exists
- Hold new direction until Ennio returns