Application Engineering · core
2D/3D Interactive Systems
Scene graphs, render loops, input, animation, physics, GPU pipelines, asset loading, and performance budgets.
Mental model
Interactive systems turn state into frames under a deadline. Separate simulation and rendering, budget CPU/GPU work, stream assets, and measure frame-time variance.
How to study 2D/3D Interactive Systems
Begin by restating the mental model in your own words, then connect it to a concrete system you have built or operated. Name the mechanism, the constraint it addresses, and the trade-off it introduces. Use WebGPU specification (W3C), Gaffer On Games (Glenn Fiedler) — Fix Your Timestep!, Game Programming Patterns (Nystrom) — chapter: Game Loop to check details, but close the source before writing your explanation. Retrieval is the learning step; rereading is only preparation.
Next, compare 2D/3D Interactive Systems with Game/Simulation Design, Product Analytics. Ask what changes in correctness, latency, resource use, operability, and failure recovery. Complete Design exercise: 2D/3D Interactive Systems and preserve the command, input, output, and one failed attempt as evidence. Finish by explaining the idea without jargon to someone who has not studied the track.
Proof of understanding
- Explain the mechanism from first principles and identify the state it reads or changes.
- Give one situation where the concept is the right choice and one where it is not.
- Predict a realistic failure mode before running the drill, then compare the prediction with evidence.
- Connect the result to a roadmap or build artifact instead of treating the concept as isolated trivia.
Learn from primary sources
Practice and explain it back
Design exercise: 2D/3D Interactive Systems
Scene graphs, render loops, input, animation, physics, GPU pipelines, asset loading, and performance budgets. Implement designOutline() returning non-empty values for: sceneState, renderLoop, frameBudget. Each value must name a concrete mechanism or decision.
Expected evidence: A design outline with sceneState, renderLoop, frameBudget plus an explicit failure mode or trade-off.
Open the interactive drill →Review prompts
- Why is simulation usually stepped at a fixed timestep while rendering runs as fast as it can?
Build evidence
Synthesize: Application Engineering
Turn backend, client, UX, real-time, interactive, analytics, and distribution skills into one complete product. Produce one working system, benchmark, or evidence-backed design that integrates the path.
- Implements or precisely models the core mechanisms from all three milestones
- Includes at least one injected failure or adversarial case and demonstrates recovery
- Reports quality, latency, resource, reliability, or usability measurements relevant to the domain
- Ships a concise architecture note explaining decisions, trade-offs, and remaining risks