May 25th, 2009 by Arjan Olsder Posted in Platforms: iOS | No Comments »
The folks over at Slide 2 Play have written an excellent editorial about 10 things mobile game developers should keep in mind to make sure that their mobile game will not cause frustration toward the consumer.
Though their editorial is focused on the iPhone, we feel most of their statements (if not all) would apply to mobile games in general.
In short, it comes down to the following; when the iPhone is on mute, don’t play sounds in your game. Allow your game to freeze and continue on next run (we know most other phones allow multitasking). Make sure thumbs are not in the way of action on the screen (since the screen is also the primary input device). When porting to iPhone, keep the iPhone special features in mind. Test software well before deploying it. Don’t make big jumps in pricing as that frustrates consumers after a purchase. Provide access to the music library on the device instead of using just your own loops. Don’t implement the accelerometer just to support it. Connect to social networks and finally, think of the colorblind and deaf people (though what’s the fun of an iPhone without being able to hear the music).
Read the full story here.
Congratulations
Your first AWS Elastic Beanstalk Node.js application is now running on your own dedicated environment in the AWS Cloud
This environment is launched with Elastic Beanstalk Node.js Platform
What’s Next?
- AWS Elastic Beanstalk overview
- AWS Elastic Beanstalk concepts
- Deploy an Express Application to AWS Elastic Beanstalk
- Deploy an Express Application with Amazon ElastiCache to AWS Elastic Beanstalk
- Deploy a Geddy Application with Amazon ElastiCache to AWS Elastic Beanstalk
- Customizing and Configuring a Node.js Container
- Working with Logs
