HTML5 Mobile GamesLTT Real Lessons Learned

LIFETIME technologies Co., Ltd.

Luu Thanh Tuan (B.SE)

Why HTML5 mobile game projectsare prone to failure?

Question

How much the gap is eventually produced

after your initial project plan?

Why HTML5 mobile game projectsare prone to failure?

Compare to the initial plan, eventually it is

1.2 times?

1.5 times?

Or maybe, 2 times?

Why HTML5 mobile game projectsare prone to failure?

Oooh,

such sweet numbers :D

• Changes in scope x 1.5 times

• Task analyzing errorx 1.4 times

• Estimating errorx 1.3 times

• One day working time expecting error

x 1.25 times

• Manpower planning errorx 1.75 times

• Quality management errorx 1.3 times

• Technology management errorx 1.3 times

• . . .

Example

1.5 x 1.4 x 1.3 x 1.25 x 1.75 x 1.3 x 1.3

≒ 10 times!!!

Why HTML5 mobile game projectsare prone to failure?

The HTML5 Mobile “ILLUSION”

1. Crappy canvas performance

2. No WebGL

3. No multi-touch in Android

4. Sound support so bad

5. Limited & terrible debugging tools

Now, On Mobile…

1. Canvas performance is solid (iOS 6+, Android 4+)

2. No WebGL, but OpenGL ES-based native wrappers

3. Multi-touch in Android 4+ now

4. Web Audio API in iOS 6+

5. Remote debugging in iOS 6+, Chrome Android 4+

There’re some good HTML5 Mobile Engines

1. Pixi.js

2. Cocos2d-JS

3. enchant.js

4. Artic.js

5. CreateJS

6. . . .

BUT… REMEMBERHTML5 is NOT a SUPERMAN