Technology used to build it
- Next.js
- TypeScript
- Cloudflare Workers
- Game data pipeline
- Mobile PWA
Public demoKBO game companionPublic demo in 2026
Public demo in development
DUGOUT 9
A KBO fan service connecting today's game with baseball memory
After choosing a team, fans can open a game room for starters, lineups, recent form, source-linked updates, and postgame review, then continue into team history, quizzes, player guessing, and connection puzzles.
DUGOUT 9 is an independent fan project, not an official KBO service. The public demo is accessible today, while data-use boundaries, team trademark presentation, durable accounts and storage, and operator permissions still need to be completed before live operation.
Service development record
How today's game context and a fan's baseball memory became one flow
The product brings scattered game information and fan content into a team-first game room, then adapts the experience across pregame, live, and postgame moments while designing a reason to return.
- 01Observation & evidence
What matters today and what fans remember live in different places
- Question examined
- Why must a KBO fan move across several screens to prepare for today's game?
- Decision made
- Treat schedules, player records, recent form, source-linked updates, and team memory as parts of one game experience rather than separate destinations.
- Evidence used for the decision
- Game centers, statistics, news, and club content are distributed across different sources, leaving fans to assemble the viewing context themselves.
- 02Problem & principle
A team companion rather than another scoreboard
- Question examined
- What distinct value can the product offer without repeating scores and record tables?
- Decision made
- Explain what to watch from the chosen team's perspective instead of listing every number, and pair data with its source and reference time.
- Evidence used for the decision
- Connecting starters, batting order, and recent form into viewing points—and comparing them with the result afterward—created a clearer product difference than competing on breaking updates.
- 03Hypothesis & scope
From choosing a team to opening today's game room
- Question examined
- Which core journey must the first public demo complete?
- Decision made
- Make team selection and the moment-aware game room the core, while team history, quizzes, and puzzles support the return loop around the game.
- Evidence used for the decision
- The first promise became ‘see today's game for my team more clearly,’ not ‘solve a large collection of baseball questions.’
- 04Experience & system
A mobile data product that changes with the game
- Question examined
- How can external game data become a source-aware mobile experience that remains useful when a dependency fails?
- Decision made
- Use Next.js and TypeScript to collect and normalize data, freeze pregame reports, expose fresh and delayed states, and connect Cloudflare storage and queue boundaries with a mobile PWA experience.
- Evidence used for the decision
- Source links, refresh windows, an in-memory fallback, and D1, R2, and Queues integration points are separated in code so missing data is not replaced with invented figures.
- 05Launch & learning
The distance between an accessible demo and an operable service
- Question examined
- What must be completed before the public demo can become a service designed to operate for the long term?
- Decision made
- Prioritize data-use boundaries, durable storage, real accounts, and operator permissions over adding more feature breadth.
- Evidence used for the decision
- The public interface and game-data connection work, but report storage currently falls back to memory while accounts, rankings, and admin state remain local demos, so operating maturity or performance is not claimed.
Signals used for the next decision
- Current focus
- A reason to return around game day
- Current stage
- Public demo · in development
- Next decision
- Complete rights review and durable operations
These are inputs for the next operating or validation decision, not outcomes already achieved.
Conditions remaining before live operation
- Review KBO data use and team trademark presentation
- Connect durable report storage and the scheduled collection worker
- Implement real accounts, rankings, operator permissions, and review history
Notes connected to this service
The question I want feedback on now
What do you check first when preparing to watch your team's game, and what would make you return after the final out?
Leave feedback