Over a million developers have joined DZone.

Debunking the Myths Surrounding Android Monetization

DZone 's Guide to

Debunking the Myths Surrounding Android Monetization

· Java Zone ·
Free Resource

If you're in the mobile development business, monetization is probably a fairly important issue to you. Why put months of work into an app if you're only going to get $344 for it, right? And it's a particularly pertinent issue if you're an Android developer, because we've been hearing for years now how Android users don't spend money, at least compared to iOS users. Something like this:

These numbers are fairly old, and the sample size isn't much, but regardless, it reflects the common understanding of mobile monetization. But according to Kevin Quach on Avocarrot, it's all a bit misleading. In this recent post, he explores five myths surrounding Android monetization, most of which are presented as criticisms of the conventional wisdom regarding mobile development and money. The key, according to Quach, is the sheer number of Android users:

More than half of the world’s mobile users are firmly in the Android camp and the percentage is still growing. In certain Asian markets, Android OS powers more than 90% of all phones – which means this platform is actually better for globally-based monetization strategies. It doesn’t take a genius to figure out how to play the numbers and make money in such a huge pool of users, even with the level of competition that mobile apps regularly face.

Other tips cover issues such as perceptions of mass appeal, imitation of major players, aggressiveness of monetization efforts, and more. In other words, it's more of a list of things not to do than it is a list of ways to rake in the cash, but either way, it is encouraging for Android developers. Take a look at the full list to get all the details.

Or, if you're still concerned, just switch over to iOS and mine Bitcoin. Problem solved.


Opinions expressed by DZone contributors are their own.

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}