Files
loto/web/docs/development-roadmap.md
T
tiennm99 d08f25bd96 feat: three-mode display (player/master/both) with master auto-tick
- Add `mode` setting to replace legacy `masterMode` with migration path
- Implement 3-button display mode picker (player-only, master-only, both)
- Auto-increment master when card drawn via call-bus event system
- Add voice hint on settings button, gate auto-call on mode changes
- Broadcast draw events from MasterPanel, reset call-bus on new game
- Broadened announce condition to cover both modes
- New call-bus.svelte.js module for event coordination
- Update settings-store tests to cover mode migration
- Update codebase docs for mode setting and call-bus architecture
2026-04-27 10:51:08 +07:00

3.7 KiB
Raw Blame History

Development Roadmap

This document tracks future work only. Completed features live in git commit history and plans/, not here. For "what's in the app right now", see docs/project-overview-pdr.md and docs/codebase-summary.md.

Shipped

Three-Mode Rendering + Master Auto-Tick (2026-04-27)

  • mode: "player" | "master" | "both" replaces masterMode: boolean
  • New call-bus.svelte.js coordinates master draws → player auto-tick in "both" mode
  • "Quản trò đọc số" voice now speaks Chờ/Kinh on master in "both" mode
  • One-shot migration: masterMode: truemode: "both"

Idea Phase

Undo Last Cell

Allow player to undo the most recent cross/uncross action. Requires change history or state snapshot. Status: Idea (low priority)

PWA Install

Add service worker and manifest for "Install App" prompt on Android/iOS. Status: Idea (would require server-side components)

Considered Phase

Multiplayer Sync (Real-time)

Host and players connect via WebSocket to sync called numbers and state. Requires backend server. Would enable:

  • Decoupled devices (players' phones, host's laptop on big screen)
  • Remote tournaments
  • Master board auto-updates all players in real-time

Consideration: Out of scope for static export. Requires major refactor (SvelteKit API routes + WebSocket server). Deferred indefinitely.

i18n Beyond Vietnamese

Internationalization (English, Chinese, etc.). Requires extraction of all Vietnamese strings and i18n library (next-intl). Status: Considered (low demand for non-Vietnamese users)

Undo/Redo System

Full undo/redo stack with history navigation. Adds complexity to state management. Status: Considered (YAGNI for now)

Testing

Component Tests (Planned)

  • PlayerBoard with mocked localStorage, $state/$derived verification
  • MasterPanel with different game states

E2E Tests

  • Player flow: generate card → click cells → verify bingo popup
  • Host flow: new game → draw numbers → verify board state

Tech: Playwright

Future Enhancements (Speculative)

Export/Import Card

Allow player to export their grid as image or JSON, import someone else's card. Use Canvas API or print-friendly CSS.

Leaderboard / Stats

Track games won, time per bingo, etc. Requires server-side persistence. Out of scope for static export.

Accessibility Improvements

  • ARIA labels for grid cells
  • Keyboard navigation (arrow keys to move, Enter to toggle)
  • Screen reader support

Custom Number Range

Host selects range (e.g., 175 for American bingo) instead of hardcoded 190. Requires config UI and refactor of game logic constants. Out of scope per Lô tô hội chợ Tân Tân focus.

Different Grid Sizes

Support 8×8 or 10×10 grids, or 3×9 European Bingo 90 tickets. Out of scope — variant locked to 9×9 Tân Tân format.

Two-line / Full-house Win Tiers

European Bingo 90 patterns. Out of scope — Tân Tân uses single-line "Kinh!" only.


Decision Rationale

All decisions follow YAGNI (You Aren't Gonna Need It), KISS (Keep It Simple), DRY (Don't Repeat Yourself):

  • No multiplayer sync → adds server dependency, breaks static export (Cloudflare Pages)
  • No i18n → Vietnamese-only community, localizing adds complexity
  • Unit tests implemented → critical paths (constraints, persistence, settings) now have automated coverage
  • Component/E2E tests deferred → small codebase, manual testing sufficient for UI flows
  • No undo/redo → simple game, mistakes are play experience
  • Svelte 5 runes → cleaner reactivity than hooks, smaller mental model

Future work gates on real user demand, not speculation.

Last reviewed: 2026-04-27 Last synced: 2026-04-27 (6-phase refactor)