What design components would need to be altered in order to deliver a game as an HTML5 vs. mobile game?

What will be an ideal response?

Even if an HTML5-based game is being played on a smartphone, it will need to be developed within the structure of that device’s native browser. The speed of the game may be an issue. Currently, HTML5 is expected to reach par¬ity with natively developed apps. This means that an HTML5 app should run just as well and as fast as an iOS or Android app. However, when it comes to game design, building a clean and efficient product is always the best way to go. Games on mobile devices utilize touch as part of their control scheme, while online games using HTML5 use mouse clicks and rollovers. Web-based players will have keyboards at their fingertips, while using the virtual keyboard on a touchscreen device is not recommended (unless the game focuses specifically on typing). Mobile games often use the accelerometer, vibration setting, or global positioning system (GPS) – all of which will not be viable in an HTML5 game. A good rule when moving from mobile to HTML5 is to refrain from tactile design and increase audio and video feedback – to compensate and keep players engaged. (Instructors might also want to have students refer to Chapter 6 [Mobile] for this exercise.)