Runtime Spike / Plain Canvas
FIELD GOAL UNLOCK in plain Canvas.
This no-write lab keeps React as the product shell and uses Canvas only for the high-motion game core: moving hit line, ball path, ghost frames, landing ring, and score feedback.
React shell
Copy, CTA, notes, safe areas, and admin-style chrome stay React.
Canvas core
Pixel motion, path drawing, ghost balls, and impact timing run in one loop.
No writes
Preview points only. No reward grant, no participation mutation.
Visible causality
Wind, tap position, landing point, and accuracy are intentionally linked.
Score
0
Last
Ready
Mode
No-write
What to judge
Does this feel more causal and game-like than the SVG path? If yes, Canvas is a good candidate for high-motion cores while React keeps the factory shell and admin-controlled skin.