Stacks are temporary contracts between you, your players, and your calendar. The “best” stack is the one that lets you ship your current loop with the fewest unknowns.
Decision axes
- Time to first input — how fast from
git initto moving sprite. - AI leverage — does your assistant know the framework’s idioms?
- Deploy shape — static, server, or hybrid.
- Escape hatch — can you eject without rewriting everything?
Three tiers we recommend
| Tier | Good for | Watch-outs |
|---|---|---|
| Canvas/DOM micro | Weekend toys, learning | You own all systems |
| Phaser/Kaboom mid | Jam + early access | Scope creep into RPG features |
| Full engine (Godot export web) | Content-heavy | Build size, load time |
When to switch
Switch when two of these hurt: tooling friction, perf ceiling, hiring/collab needs, or port targets (mobile wrapper).
FAQ
TypeScript everywhere? Prefer yes for multi-file games; JS is fine for small toys under 500 lines of code.
Do hubs care about stack? Players care about playability; builders browse stacks on AI tools and developer profiles.
Next steps
- Browse vibe-coded games for proof of what ships.
- Commit to a game jam date.
YGG Play helps you pick boring-winning stacks.
