Keep simulation independent from rendering
A fixed-step simulation and seeded traffic make gameplay rules testable without a browser renderer; this is an update interval, not a measured frame-rate guarantee.
Air Traffic Control
desktop app
A browser, Windows, and Linux arcade game that separates flight simulation, rendering, and local progression so routing rules remain testable across delivery targets.
- Role
- Game design and TypeScript engineering
- Scope
- Traffic simulation, pointer routing, local progression, browser delivery, and Windows and Linux desktop distribution
- Status
- Browser deployment, Microsoft Store distribution for Windows, and Snap Store distribution for Linux
1 / 5
Problem
A flight-path drawing game needs collision and landing rules that agree with what players see, while keeping progress meaningful across short sessions and different screen layouts.
Constraints
- C1
Flight paths require mouse, touch, or pen input; keyboard navigation alone does not cover gameplay.
- C2
Browser and desktop saves are separate and local, with no cloud sync or save export.
- C3
Browser offline play requires an initial online visit and successful asset caching.
- C4
Resizing or changing orientation can invalidate an active airfield layout; broader real-device testing and difficulty tuning remain ongoing.
Architecture
A framework-independent TypeScript simulation feeds Phaser rendering and pointer interactions. DOM menus coordinate sessions, IndexedDB persists local progression, and Vite builds browser and Electron delivery targets.
01
Simulation
Fixed-step updates at 1/60 second, seeded random traffic, flight-path geometry, and aircraft-shaped collision polygons live outside Phaser.
02
Interaction and rendering
Phaser scenes render airfields and aircraft, while pointer routes guide aircraft to matching landing zones. DOM menus expose difficulty, career, achievements, and settings.
03
Local progression
IndexedDB stores versioned saves, career progression, achievements, and records. Completed shifts contribute progress; practice and abandoned shifts do not.
04
Delivery
Vite and a service worker support cached browser play. Electron loads bundled assets through a restricted custom protocol, with AppImage and Snap packaging for Linux. Windows players can install the game from the Microsoft Store.
Decisions
Match collisions to visible aircraft
Collision outlines follow the airframe heading and exclude selection halos, shadows, and rotor blur so visual effects do not become fatal collision surfaces.
Commit progression at session completion
Recording outcomes only when a shift finishes keeps practice, restarts, and abandoned sessions from inflating career progress.
Ship the same game with explicit storage boundaries
The browser uses cached assets and site-local saves; the desktop app bundles assets and maintains separate local saves rather than implying cross-device synchronization.
Contribution
- Implemented aircraft routing, traffic pacing, landing checks, and collision geometry.
- Built nine airfields, three difficulty levels, seven career ranks, and nine achievements.
- Integrated IndexedDB persistence, offline browser assets, and desktop distribution for Windows and Linux.
- Added automated coverage for simulation, progression, storage, audio, and UI behavior.
Outcomes
- Players can draw routes for three aircraft types across nine airfields in the browser or Windows and Linux desktop apps.
- Local career progression and achievements persist between completed sessions without requiring an account.
- The simulation can be tested independently of Phaser rendering.
- The product provides a browser entry point, a Microsoft Store installation path for Windows, and a Snap Store installation path for Linux.
Product screenshots
1 / 5
Verified stack
- TypeScript
- Phaser
- Vite
- Electron
- IndexedDB
- Progressive Web App
- Vitest
- Playwright
Working through something similar?
Share your challenge, scope, and timeline to start a focused conversation.