February 15th, 2009 by Arjan Olsder Posted in Marketing Strategies | No Comments »
Mpowerplayer shared insights collected from the recent launch of its Mplayit Mobile Arcade application on Facebook and MySpace. The application allows consumers to discover and try mobile games directly from their Web browser.
Sampled from more than 50,000 users, the audience on the Mplayit Mobile Arcade is nearly two-thirds (65 percent) female, and more than half are between the ages of 18 and 34.
Nearly every visitor tries out the games, while a larger number return to check out new games as they are added to the catalogue. Mplayit Mobile Arcade users also show intentions to purchase the titles. On average, one in every eight games played (14 percent) produces a click to buy, while the top titles perform at a ratio of one in three (33 percent).
The most popular games played and recommended on the Mplayit Mobile Arcade are evergreen casual titles like Bejeweled and arcade classics like Ms. Pac Man.
"This is a difficult demographic to target because they're not inclined to waste time trying to find a game on their phone," Powers said. "However, when we show them that their favorite web games are available for their phone, they get interested. And when you add the social element and the content is recommended by their friends, they don't hold back. People want to find mobile content in the same way that they find web content: on the recommendations of their peers. We are leading the way in socializing mobile content."
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