Last week Flurry released an interesting chart on the Freemium games .
As evident, the data suggests that max amount of money (49%) is spent by users in the 25-34 age group. They play only for 29% of the relative time. One possible reason is that this demographic prefers to buy upgrades and special powers to help them cross levels faster. In the same light, the 18-24 years age group spends the max amount of time (32%) but only 16% of the relative revenue comes from them. This is even lower than than the 28% revenue coming from the 35-54 year age group which spends only 14% of the relative time.
While 13-24 year olds constitute more than 50% of the time spent, they contribute only 21% to the revenue. This is an interesting observations for gaming companies. It helps them understand that they can make more money by catering to the in-app purchases of this higher age group (24-54 years).
Flurry had earlier published that consumers spend an average of $14 per transaction when making in-app purchases in freemium games. What items does this money go to? Another interesting chart shows the spending on durable v/s consumable good.
Durable goods are those which can be use to provide permanent benefit in the game play and consumable provide only one time benefit. Personalized are those which are only for a purely decorative purpose. Consumable goods constitute more than 50% of all in-app purchased in freemium games. A majority of this is a towards game currency which can be used in multiple ways within the game.
The data cannot be generalized completely and should be taken with a pinch of salt. Depending on the actual game needs the attractiveness of the durable and goods will change.
The two sets of analysis above are important when trying to decide what in-app purchases to offer and what age groups to cater to. With 65% of all revenue generated among the top 100 games now coming from freemium games these numbers become even more important to understand.
Wednesday, September 14, 2011
Wednesday, September 7, 2011
HTML5 v/s Native Apps
With more and more companies putting in thousands and thousands of $$$ on their mobile initiatives, the big question about the mobile road map is : HTML5 or Native Mobile apps?
In one of my earlier posts, I discussed some factors which will help a company decide whether to opt for a Mobile website or a Native app. The current question becomes more interesting because of the present state and buzz about HTML5.
What is HTML5?
HTML5 is the fifth version of the HTML language that provides the basic building blocks of web pages. It will support multimedia without plugins and has the ability to work on all computers and devices.
Advantages of HTML5
Few HTML5 Limitations
Some quick tips to help you decide:
In one of my earlier posts, I discussed some factors which will help a company decide whether to opt for a Mobile website or a Native app. The current question becomes more interesting because of the present state and buzz about HTML5.
What is HTML5?
HTML5 is the fifth version of the HTML language that provides the basic building blocks of web pages. It will support multimedia without plugins and has the ability to work on all computers and devices.
Advantages of HTML5
- Portability: HTML5 web apps can be accessed and used on any device via a web browser, much like a mobile website
- Cost effective: They can turn out to be significantly cheaper that developing native apps for various devices
- Offline access: Web apps also provide the capability for offline access and usage via application cache, meaning you don’t have to have a network connection to use them.
- HTML5 introduces new APIs to access mobile device functionality, in particular sensors such as accelerometer and GPS
Few HTML5 Limitations
- Security issues: Users could tamper with processing scripts, which might allow unauthorized access. Hackers can get access to perks, discounts, etc. for which they really aren’t eligible.
- Synchronization challenges: While the app is connected, it can save data to the cloud however if it goes offline, changes will not get saved. Synchronization can become a challenge when people access from different devices.
- User Experience: Mobile apps are a lot about the user experience. Its really crucial how well you can engage your user with such a small screen. Native apps till date offer a better user experience, ease of use and convenience.
- Standard Gestures: Some standard actions specific to a device will not be supported by HTML5. For eg: iPhone has the standard 'long hold' which is used for many actions. The HTML5 look and feel will be like the web feel.
- Marketing effort: This is specially crucial for smaller companies who attract many of their users from the various app stores.
- Monetization: The fact that apps like Angry Birds have made millions of $ is possible only because of an app store which lets people discover them and developer monetize them. This is not so easy on HTML5.
Some quick tips to help you decide:
- If your app is very complex and highly interactive, use native
- If you are targeting multiple platforms and your offering/ value is web-centric, use HTML5
- A native app can also have web view, so consider a 'hybrid app', if required
- Consider one or both options based on the company and user requirements and your budget and target.
Subscribe to:
Posts (Atom)