Best practices

try the airconsole checklist before submitting your game! general try to test your game on as many as different phones and screens as possible make sure all resources (external js, css files etc ) can be loaded over https games shouldn't request a separate login having problems during development? check the airconsole tag on stackoverflow somebody might have had the same issue before controller technical use \<div> \<div> tags with a background image style as buttons instead of \<input> \<input> or \<img> \<img> tags use touchstart touchstart and touchend touchend for event handlers instead of click click or mousedown mousedown var button = document getelementbyid('button 1'); button addeventlistener('touchstart', touchdownhandler); button addeventlistener('touchend', touchendhandler); or try the airconsole controls library, which already takes care of this preload your images in the beginning // for example in javascript var images = \['button 1 png', 'button 2 png', 'character 1 png']; for (var i=0; i < images length; i++) { var img = new image(); img src = 'assets/images' + images\[i]; } use the airconsole keyboard for text input on the device, since the regular keyboard can cause a lot of rendering issues controller design always indicate which ingame character the player is controlling e g if the player is controlling the blue character in the game, then make the controller interface blue avoid having unnecessary buttons e g you can just go left and right, so you don’t need a 4 directional dpad show different states on the phone instead of always showing the ingame controller if a player dies in the game and the game is still running, then show a “you are dead” view on the players controller make sure the user flow works from menu > game > game end > menu screen / game explain your game to your players e g with an intro screen or a tutorial make sure that it's not too easy to skip the instruction screen by accident check what happens if a player joins or leaves during a running game if your game needs more than 1 player, display it in the start screen if your game has a max player amount, display a “max player reached” if too many players connected do not use device ids as player numbers device ids may not be consecutive, there may be devices that were connected but have left read more instead of showing "player 1", try to show the real player name ( (airconsole getnickname() (airconsole getnickname() ) be aware that players may have a high latency unity export your game early and often! some issues may not appear in the editor and cause unpleasant surprises if you export it for the first time right before launch time images and javascripts need to be in webgltemplates/airconsole webgltemplates/airconsole so your screen and controller can access them in the exported build use the profiler to pinpoint performance issues and optimize them read up on the limitations of webgl early enough so you don’t spend time on features that can’t be used in the exported version having memory issues? can you reduce the number of gameobjects in your game, for example? if not, consider increasing the memory size in build settings > publishing settings avoid exceptions at all costs, because they will cause crashes in the webgl export if you’re getting an exception and don’t know why, make a debug build with build settings > publishing settings > enable exceptions set to “full” and then look at the console in your browser to see a precise error message