This document discusses the capabilities of rich browsers and devices for building games, including new browser APIs for graphics, audio, and device access. It also touches on challenges like browser fragmentation and differences between desktop and mobile browsers. An example architecture is proposed using a Node.js server to synchronize game state over web sockets between HTML5 mobile and desktop browsers.

1. GUIDO GARCÍA · GUIDO@TID.ES · @PALMERABOLLO
DEC. 2011

2. RICH
BROWSERS
CANVAS · WEB SOCKETS · WEB WORKERS ·
WEBGL · LOCAL STORAGE · VIBRATION API · WEB
AUDIO API · GAMEPAD API · MOUSE LOCK API ·
FULLSCREEN API · GEOLOCATION · ...

3. RICH
DEVICES
TOUCH · CAMERA · ACCELEROMETER ·
GYROSCOPE · ROTATION · PROXIMITY ·
BAROMETER · LIGHT · TEMPERATURE ·
MAGNETIC FIELD · ...

4. NEW
SERVERS
NODE.JS + SOCKET.IO + NOWJS + EXPRESS + JADE
= DEV PRODUCTIVITY + PERFORMANCE + FUN

5. BROWSER
FRAGMENT
ATION
BAD IMPLEMENTATIONS · CUSTOM APIS
W3C TOO SLOW · GOOGLE / APPLE TOO FAST
NORMALIZATION (DAPJS · SOUNDMANAGER)

6. DEMO
DESKTOP BROSWER (CANVAS) = GAME ARENA
MOBILE BROWSER = GAME CONTROLLER

7. ARCHITECTURE
node.js
server
HTML5
HTML5
mobile
HTML5 HTML5
mobile ws:// ws://
player
mobile canvas
player
players
game
state
touch = shot
change orientation = reload