Picking the Right Tool for the Job: HTML5 vs Unity
summary
Compares a single game built twice: once in Phaser (HTML5) and once in Unity, showing HTML5 excels for fast prototyping and casual games but suffers fragmented frameworks, inconsistent mobile performance, and heavy tool-building, while Unity gives drag‑and‑drop editor, native speed and one-click publishing at the cost of vendor lock‑in and paid modules; demonstrates responsive game design across resolutions and inputs, and a real publishing path via Amazon where Amazon Underground pays per minute, noting more developers beat the $500/month app store poverty line.
AI-written summary · about
chapters (6)
- 0:00Introduction
- 10:00Single codebase multiplatform
- 17:24HTML5 game frameworks
- 20:31Unity game development
- 27:36Amazon Appstore publishing
- 35:58Q&A
related talks
32mUnity + HTML5 = Isomorphic Game Engine?
29mLet's make games with JavaScript
34mThe past, present, and the future of HTML5 game development
38mWhat if we made a game?
20mHTML5 for Mobile Games
17mNot Everything is a Nail When You’re Making Games
26mdeveloping videogames in JavaScript
37mHTML5 Game Engine development