Take a look at your folder of game-ready art assets. Did you manage to keep the whole set under 10 MB? If so, what techniques did you use to optimize the art?

What will be an ideal response?

Students should review their game-ready art assets and verify that they kept the entire set under 10 MB. One of the key restrictions on consoles and standalone desktops is the amount of available memory space (a key design fac¬tor when designing for those platforms). However, HTML5 is web-delivered content—and web browsers are optimized for pretty pictures, not for running complex math on the fly. It is bet¬ter for the initial load to take an extra second (to bring in more art assets) than for your game to lag at a crucial point. It’s important to optimize your graphics beforehand; don’t trust the machine to do this for you. This means taking out any unnecessary blending or dithering. If you don’t need that edge anti-aliased, trim it down. Think twice before you blow all those pixels on a nice smooth gradient. It’s also important to use elements more than once. If you have a bouncing beach ball in only one room of one level out of 25, think twice. Is there another pre-existing in-game element that will serve the same purpose? Keep unique elements at a minimum without harming your gameplay.