Game Framework

LAB / EXPLORATION

Reusable Browser Game Architecture
Reusable browser-game foundation for scenes, state, input, sprites, and simulation systems.

PLANNED LAB

Extract reusable game architecture from small experiments so future browser games share a clean foundation. The implementation is planned.

PLANNED LAB

Extract reusable game architecture from small experiments so future browser games share a clean foundation. The implementation is planned.

Why this project exists and what the implementation should teach.

Purpose / Learning

Purpose

Extract reusable game architecture from small experiments so future browser games share a clean foundation.

Learning Objectives

Separate game state from rendering.
Define scene or mode transitions.
Centralize input handling.
Manage sprite/state mapping.
Create reusable timing and update-loop utilities.
Support simulation-oriented projects such as Bird Life without hard-coding one game.

Current, planned, legacy, or candidate technologies for this project.

Language Candidates

TypeScript
JavaScript

Rendering Candidates

Canvas 2D
Phaser

Data

JSON

Optional

Web Audio API

Planned behaviors, architecture decisions, and evidence this project should produce.

Core loop

Provide predictable update and render stages.

State

Represent game and entity state independently from drawing.

Input

Normalize input for game code.

Assets and sprites

Map visual assets to entity state.

Reuse

Prove the framework with at least one real game.

Implementation context, boundaries, and later expansion.

Project Notes

Engine Decision

Phaser remains a candidate, but a lightweight Canvas-first framework may teach more fundamentals.

Scope Boundary

Build only abstractions that a real game immediately uses.