I see a lot of user coming here with problems like
</br>
1)Game runs super slow on device
2)Black screen game won't run
3) Loading takes forever
</br>
So here are some thing to consider when making a mobile game run faster.
1) Resolution= the best resolution is 650,350 or 800x480 once you start going into 960x640 your in game graphics will be much larger and take longer to load. Yes you can make a smooth running game at higher resolutions but it will be much harder.
2) Tilebackgrounds= you should always make your background into tiledbackgrounds . Using sprites will cause higher running memory usage.
3) Collision Checks= Construct2 is great at detecting collisions in a pixel perfect way. That said if you have sprites that don't have collision events, turn off the collision detection. That will be one less collision that your device has to compute and check for.
4) Graphics Size= Make your graphics the right size for example don't make a 400x400 sprite then resize it in the layout screen to 200x200. No the memory footprint is still 400x400 . Go into your graphics editor like gimp and resize the sprite correctly. If too many graphics are too big, you will get the black screen.
5) Event Sheets= Now this is tricky so please read very carefully. If you have 10 levels in a game you don't need 10 event sheets, repeating some of same code over and over in each sheet while adding new code to the next sheet. Instead for example have 3 sheets 1 for game events, 1 for player events, one for enemy events. Now in the game events sheet go to the top of the event sheet , right click on mouse a menu pops-up then select include event sheet. Now for each layout you can select the game events sheet and the other event sheets are included.
6) Timers= Be careful in using too many timers in your game. I use timers in all my games and can get away with using 7-8 timers per level with no performance problems just some glitches none game breaking.
7) Coding= over time learn how to minimize coding so there is less code your device has to run through to get information. I suggest you learn if and else statements to cut down on code.
8) Destroy Non used sprites= If you have a bullet flying offscreen and its never destroyed, it will keep using memory. If you have game elements that go offscreen you must put a destroy code so that each non used sprite is destroyed when not in the field of use.
Example of game that uses 2-3 timers per level ,bullets flying left and right, 3-6 enemies per screen, larger graphics images, and still runs smooth then try my game to see
https://play.google.com/store/apps/deta ... ion.undead
Any questions or anything you feel I forgot just let me know.