119 Challenge
A timing-sense game where you stop exactly at 11.900 seconds - an MVP for an SKKU EMBA event.
- React
- FastAPI
- Render
Entry screen - the one-line rule ("stop as close to 11.900 as you can") and a name field, nothing else
Name confirmation - a typo becomes the leaderboard and prize name, so we confirm once
Right before start - only the 11.900 target shows, with a single start button
Mid-attempt - the "focus" copy plus a large timer; the stop button stays pinned at the bottom
Result - the gap from 11.900 (0.009s), the score (9,991), and the grade (S) on one screen
Ranking - 1st/2nd/3rd podium with a personal-best alert; live updates so you see the next seat break a record
- Problem
Needed a short, intuitive game that pulls people into an offline event. A long rule explanation breaks the queue.
- Context
A fast MVP built for on-site use at a grad-school (SKKU EMBA) event.
- What I did
- Single-interaction game where you stop as close to 11.900 seconds as possible
- Real-time ranking, podium, and record-broken alerts
- Product decisions
- Rules in one line ("stop at 11.900") - first-entry friction near zero
- Live ranking updates - the moment the person next to you takes the lead is the trigger to try again
- Metrics
Used multiple times on-site at the event; exact participant numbers not collected.
- Outlook
Built for a single event. The model could apply to other events; nothing committed.
- QA lens on this call
In a timing game, measurement accuracy is reliability. Lowered the dependency on the client clock and adopted server-time-based verification early.
- Tech stack
- React
- FastAPI
- Render