HTML5 technologies and game development
summary
Survey of playable HTML5 work that actually ships and runs: a playable, open source MMO Browser Quest uses Node.js and websockets for real time multiplayer and it works; mobile ports like Cut the Rope and Gameloft’s GT Racing use WebGL or canvas plus porting tools; WebGL delivers near console visuals and Tinkercad shows 3D printing from the browser; audio data API drives live visualizations; pointer lock and full screen improve immersion; the experimental Gamepad API already reads controllers in Chrome and Firefox.
AI-written summary · about
chapters (19)
- 0:00Introduction
- 1:13Games are universal
- 2:47Games are fun
- 4:07Games push boundaries
- 6:05Better web
- 6:37HTML5 games
- 10:26Canvas
- 14:29WebGL
- 17:57RequestAnimationFrame
- 19:24Audio
- 21:16Local Storage
- 24:14Web Workers
- 25:31Fullscreen API
- 27:06PointsLock API
- 28:37Gamepad API
- 32:14Orientation API
- 33:19Web Runtime
- 37:34MScript
- 39:16Resources
related talks
34mThe past, present, and the future of HTML5 game development
42mThe future of browser games with HTML5 and WebGL
20mHTML5 for Mobile Games
40mWeb Applications of the Future
29mOnce Upon A Time, Somewhere Between Your Console And Browser
34mModern Web Game Development
18mRealtime HTML5 Multiplayer Games with NodeJS
54mThrow away your Xbox - The future of games is written in JavaScript