Getting users to pay for things remains the biggest challenge for the app developer

More than half of mobile developers are living in “app poverty”: making less than $500 a month from their apps.

We’ve produced an infographic which looks at insights such as this from The Evolving State of Mobile Commerce, a report published by VisionMobile in collaboration with Braintree.

Here are some more of the insights that are featured in the infographic:

  • Half of M-commerce developers are using the App store
  • Operators are still bankers in the Middle East and Africa
  • Bitcoin is bigger in the Americas

The M-commerce Ecosystem

This is just a small sample of the insights contained in the report, if you’d like to know more, then take a look at The Evolving State of Mobile Commerce report.

Whatever happened to Operator Billing?

In 2003 Europe’s mobile operators launched Simpay, promising to let us buy flowers and concert tickets across Europe, with the price added to our mobile phone bill. By 2005 that had morphed into PayForIt, for UK operators only but with similar aspirations, and a similar lack of success. A decade later, mobile network operators are still being cut out of the payment loop, but not for lack of trying.

Operator billing should be the perfect m-commerce platform: Mobile operators store prepaid credit for 77% of their customers, according to the GSMA, and have credit agreements with the other 23%. They have experience dealing with critical systems, and real-time credit checking systems built to take huge loading, so they should be the obvious winners in the m-commerce business. As then-CEO of Vodafone Arun Sarin told the FT in 2007:

“The simple fact that we have the customer and billing relationship is a hugely powerful thing that nobody can take away from us … Whoever comes into the marketplace is going to have to work through us.”

Only they didn’t, and they don’t, and these days operator billing is a minority pastime everywhere – except Africa and the Middle East.

mobile commerce operators in Africa

The data comes from the VisionMobile Developer Economics survey, which reached more than 11,000 mobile developers at the start of 2016. Almost 2,000 of those developers are involved in m-commerce, but only 16% of those have integrated operator billing into their applications.

In Europe, where operators have perhaps tried the hardest to become the wallet of the future, that number drops to 12%, and in North America only 8% of m-commerce developers have bothered to work with the operator to handle billing. In 2010 Verizon launched its own payment service, based on the BilltoMobile platform, but BilltoMobile has been losing money ever since, and in May this year was purchased by UK payment processor Bango.

The argument against operator billing has always been that of interoperability – developers integrating with one mobile operator’s billing system would have to port their code to support another. That was the problem that Simpay, and PayforIt, were designed to solve, and they are far from alone in solving that.

The GSMA’a OneAPI started out as platform for interfacing with SMS Centres and network call management, but quickly focused into a cross-operator billing system to attract operators who proved reluctant to spend money implementing the whole standard. Even GSMA’s decision to host a OneAPI proxy (making it much easier for operators to integrate) wasn’t enough for the operators, and the standard now languishes as a vertical API within a handful of network operators.

In May 2016 yet another attempt was made, with nine of the largest mobile operators joining up to endorse the “Open API” from the TM Forum (an industry body with a decent history of setting architectural standards in infrastructure). This latest set of APIs covers a very wide remit, but includes much that the OneAPI set out to achieve including the resolution of billing events.

Other cross-operator alternatives, such as Telefónica’s BlueVia, have achieved some level of success, but it is probably too late for mobile operators to become the default billing platform they imagined that they would be. Only in the Middle East and Africa is mobile operator billing being used by a significant proportion of m-commerce developers; everywhere else that role is being filled by other players.

Just as Apple and Google provided operator-independent app stores, those companies provide the perfect alternative for developers looking to collect money. Billing through the app store itself, or via the electronic wallets run by Apple and Google, is increasingly popular – and both companies have extended the functionality in recent months.

Credit cards also remain popular. Most credit card processing is done via third-party companies, such as Braintree and Stripe, who compete to provide the best APIs and value-added services. Meanwhile various banking consortia are jumping into the frame, and Visa and MasterCard are funding various competitions intended to raise the profile of their own developer programs, and demonstrate their utility beyond basic transaction processing.

With such strong competition in place the opportunity for operators to step in and take the market is long gone, and developers won’t be easily wooed away from third-party providers. With a coordinated approach the operators certainly could have grabbed the market, but arrogance, lethargy – and the fear of creating an illegal cartel – prevented that future from happening.

The world of mobile commerce is evolving fast, and is only going to become more important as it grows and changes so rapidly, but mobile network operators will struggle to be more than a big player in it.

If you’d like to know more about which m-commerce platforms are gaining ground, or what developers are looking for in an m-commerce platform, then take a look at The evolving state of mobile commerce, a report published by VisionMobile in collaboration with Braintree.

Why are mobile developers so obsessed with advertising?

Advertising is used as a revenue stream by 38% of mobile app developers, far higher than any other source, but the majority of developers chasing the advertising dollar aren’t making much money, so what kind of developer persists in embedding adverts when the real money is elsewhere?

At VisionMobile we ask developers about every aspect of their work, the tools they use, the languages they work with, and (most importantly) what they hope to achieve by developing mobile applications. That last question is used to divide the developer community into eight segments, reflecting the motivation behind their efforts.

mobile developer segmentation

We know that across the mobile community 38% of developers are using advertising, compared to 21% who are still making money from downloads and 19% who are looking for subscription revenue. That 38% has remained pretty static over the last few years – at the start of 2015 it was 36% (see State of the Developer Nation Q1 2015) despite the lack of revenue generated (see State of the Developer Nation Q1 2016 for more details). The simplicity and scalability of advertising is irresistible to cash-strapped developers. But when we break down the numbers by developer segment some more interesting patterns emerge.

More than half of Hunters, for example, are using advertising as a revenue stream, the largest of any segment. Hunters are making money from their applications, but are always on the lookout for new opportunities or sources of revenue. As a result, they are the largest users of pay-per-download and in-app purchasing, as well as advertising. Almost a third of Hunters are using each of those business models, and more than 20% are using subscriptions too.

revenue of mobile developers segments

Hunters are clearly prepared to make money any way they can, and have harnessed multiple business models to make their product viable, but the segment also reflects an industry trend towards harnessing more than one revenue stream.

The first wave of mobile applications were largely pay to download – users were asked for a few dollars which was collected by the application store. That resulted in race to the bottom, as cheaper applications supplanted higher-quality rivals, and the cost of developing a mobile app quickly become untenable. The solution was advertising, embedded in the app as it ran or sponsoring content within the app, to cover the cost of development. That worked for a while, but as the industry grew in size the advertising revenue was spread more thinly.

In-app purchasing is another alternative, and now a foundation of most games and many other mobile applications too. Freemium models, where a basic version of an app is free, but users pay to remove adverts or add features (or both) have become increasing popular. Developers aren’t pinning their hopes on one revenue model any more, they are taking money however they can.

Digital Content Publishers are almost as polyamorous as Hunters in their exploitation of different revenue streams; subscriptions are obviously very important to them, 27% citing subscriptions as a revenue stream, but Advertising is even more significant with 34% mentioning it.

There are really two groups of developers who use advertising as a revenue source – those looking for simplicity and scalability as they dream of being the next big thing, and those who have added advertising as an additional revenue stream to top up their income.

The developer of Flappy Bird didn’t expect to make much more than pocket money when he released his childishly-simple (but challenging) game into the app stores, but (almost a year later) an unexpected surge in popularity was generating $50,000 a day for the developer. The scalability and simplicity makes advertising attractive, but very few developers manage to emulate that level of success.

For the second group, advertising is more viable – the only risk is a possible alienation of users, but that can be alleviated by offering a “premium” version for those who choose to pay. For many developers the income from advertising can form part of a revenue mix which combines to form a sustainable business.

Advertising isn’t the fairy dust it once was – giving up 10% of a mobile screen isn’t the route to riches – but neither can it be ignored as part of the mobile revenue mix, as it has become for many developers.

To gain more insights into how mobile developers can be understood through segmentation take a look at Mobile Developer Segmentation 2016, available from VisionMobile.

Will developers stop playing the app lottery?

[How long will developers be loyal to ecosystems that seemingly set them up for failure? The odds are clearly stacked against developers as most of them struggle to make a living. The sustainability of co-creator ecosystems is in serious peril, it would seem. A look at other lottery-like industries provides an explanation, and a surprising perspective.]

illu

Great news from Apple’s HQ, everyone! The App Store is breaking records (yet again, some point out), both in terms of popularity with users and in the total amount of money they spend. What an awesome time to be an app developer, isn’t it?

Well, not quite. Tim Cook doesn’t exactly paint the whole picture. The truth: all that app store goodness is very unequally distributed across developers.

The figures in our Q3 2014 State of the Developer Nation report are once again crystal clear: [tweetable]the vast majority of app developers struggle to make a living. 7 out of 10 don’t earn enough to sustain full-time development[/tweetable] (we call them the Have Nothings and Poverty Stricken). That would be over 2 million people, roughly the population of Slovenia. Almost 90% of that record app store revenue will go to just 12% of developers.

While more app store revenues are clearly a good thing for developers, the money is peanuts compared to what Apple makes. In Mobile Megatrends 2014, we showed that [tweetable]Apple captures 80% of the total iOS “ecosystem GDP”, while developers capture less than 15%[/tweetable] (including commissioned apps released without any revenue model).

The situation on Android is even worse. [tweetable]Whereas 50% of iOS developers live below the poverty line, the number for Android is 64%[/tweetable]. Also for Android, hardware makers capture 80% of ecosystem GDP, while developers are scrambling over the left-overs. Other ecosystems like Windows Phone or Blackberry don’t have the scale to provide viable escape routes.

Is this sustainable?

Can this situation continue, or will these ecosystems eventually collapse as developers get fed up? [tweetable]How long will developers be loyal to ecosystems that seemingly set them up for failure?[/tweetable]

The prospects are indeed grim. Marco Arment, for example, speaks about “vastly increased commoditization” as well as declining consulting revenues in a post titled “App Rot”. He quotes other Indie developers saying “There’s a chill wind blowing”, “The app gold rush is well over”, “In my tenth year as a full time indie dev, … I think that yes, it is much harder these days” or “Considering the enormous amount of effort I have put into these apps over the past year, [my sales figure is] depressing.” Expressions of distress that are far removed from Tim Cook’s optimism.

And yet, they’re still at it. The number of app developers shows no sign of declining.

The app lottery

[tweetable]App development is a lot like playing the lottery – as long as there is a chance to win big, people will play.[/tweetable]

Investing significant amounts of money and effort when the odds are stacked heavily against you is not a rational choice. But it’s a very human one. We’re collectively bad at assessing likelihoods, especially in situations as complex as marketing a killer app. We get as much pleasure from fantasizing about a big win as we would get from the win itself, especially if we’re poor to start with. The fantasy gets even better because we can’t imagine any other way to get this rich, this quick. The final nudge is the sense of regret we would feel if we didn’t implement that great idea we had, while someone else hits it big on the app store with that same idea. [tweetable]Rational thinking versus pleasure center lit up by fantasies? It’s no contest, really.[/tweetable]

There are plenty of other industries with the same characteristics. The same income inequality and hope-driven creation play out in music and other forms of entertainment, game development, and entrepreneurial communities (as long as there are exits, there will be wannabees). Future industries will show the same pattern, too. Internet of Things, anyone?

Ecosystems can sustain this situation as long as there is supply of developers hoping to get rich. Only 1.6% of developers have an app that earns >$500K per month, but those few big wins will make all the difference for the motivation of the Have Nothings, the Poverty Stricken and the Struggling to keep creating (source). Asking whether developer ecosystems are sustainable is like asking for how long casinos will exist given that most participants lose money. “Indefinitely” would be a safe bet.

How Samsung enlists developers to make sense of health data

Samsung unveiled its vision on mobile health. The company wants to provide the “voice of your body” with two new intiatives: a sensor-packed Simband device for protoyping next-gen wearables, and the SAMI cloud platform that enables developers to generate insights from health data. The vision is spot-on when it comes to making software entrepreneurs the new heroes of health. Analyst Stijn Schuermans asks the question: what’s next for mHealth? 

Samsung Simband Health Sensors

It used to be that the coach on the field or in the gym had all the wisdom to make you fitter and healthier. Ever since Moneyball, coaches have had a serious competitor: data. This trend has started to snowball in recent years with the advent of smartphones, wearable fitness trackers and connected devices (from scales and heart rate monitors to blood glucose meters).

Health IoT has moved from being a blue ocean market to red ocean status as competition increases. Fitness trackers, connected weight scales, sensorized running shoes… Already we see dozens of similar devices on the market. For example, Amazon.com shows 1,000+ results in the pedometer category; it lists products from Fitbit, Jawbone, Nike, Basis, Omron, iHeart, Striiv, Misfit and about 50 other known and less known brands. Even if many of these are not yet connected, they will be soon.

[tweetable]The current wave of health and fitness related IoT devices is just the beginning.[/tweetable] Once these devices become commonplace, what’s next?

From coder to coach: the role of software entrepreneurs in mHealth

It is well understood that the trend to approach fitness with devices and data will have far-reaching consequences for sports coaches, dietologists and medical professionals alike. If those professions want to remain the heroes of health in the future, they’ll need to partner up with new players in the game: software developers and data scientists.

[tweetable]The wheels are already in motion when it comes to making sense of health data.[/tweetable] There are already over 50K health apps on iOS and Android that help people to get fitter, increase their wellness or manage their disease. Insurance players like Aetna are working actively to get a full health picture. Their Carepass initiative helps their customers to get a full picture of all their app and device data in one place, and to set and track health goals. Propeller Health is combining IoT with environmental data to help patients to better manage asthma.

What’s being done for the developers who make all those apps? Programmable Web lists 100+ health APIs. Most of them are between 1 and 3 years old and will have matured quite a bit already. Companies like Human API and Validic provide middleware for health data, making it easier for software entrepreneurs to build interesting applications. Another company that has clearly understood the message is Samsung. Their “voice of the body” concept is spot on. With today’s announcement of the SAMI platform they’ve taken a big step in enabling developers to make sense of data. SAMI, an unwieldy acronym that stands for Samsung Architecture Multimodal Interactions, is described as an open cloud-based sensor data platform that helps developers to go “from big data to contextual insight”.

[tweetable]IoT and wearable will win by communities of software entrepreneurs that will make sense of all the data they generate[/tweetable] and help you improve your health, no matter what your current level of fitness is. The smartest of these entrepreneurs will combine data from many sources to arrive at the best possible recommendation or diagnosis. Platforms like Human API or Samsung’s SAMI will make that possible.

Incidentally, Samsung has signaled clearly today that developers and entrepreneurs are crucial to the future of mHealth. Developers being involved long before a consumer-ready device is available – the same developer-first strategy that Google followed with Android or, say, Google Glass. The Korean electronics giant is also putting its money where its mouth is: it will invest a handsome $50M in a Digital Health Challenge to stimulate innovation within the global developer ecosystem.

Next stop: users

Samsung’s Voice Of The Body announcements illustrate the evolution in IoT maturity nicely. First come sensors and devices, represented today by the Simband “investigational device”. (Simband is a wristband packed with novel sensors to measure your body. It’s more of a reference design rather than a commercial product.) Then, empower hardware makers, developers and entrepreneurs to experiment with the new technology (via Simband) and with the data it generates (via SAMI). Samsung obviously hopes that this will result in more component sales. But before that will happen, a final piece in the puzzle needs to fall into place.

Simband and SAMI, despite all the talk about developer-entrepreneurs, are still very much focused on solving technology challenges. The aim is to reduce the cost and complexity of building valuable applications. What’s missing is a vision on how to connect these developers and their apps to the users who needs them. Where will the demand for wearable health sensors and health apps come from?

We can draw an analogy with smartphone platforms. The Android ecosystem consist of a software platform (the Android Open Source Project, or AOSP), plus the Google Play app marketplace and a set of critical apps and APIs (more in our Naked Android article). AOSP is open, the Play store and Services are tightly controlled by Google, as they represent the connection with users. Demand for Android phones is driven by Android apps, which are built with Play APIs and available on the Play store. [tweetable]The SAMI platform represents the AOSP of wearables.[/tweetable] The equivalent of the Play services is nowhere to be seen (yet).

The crucial question for Samsung and other players in the space is this. Will they stop at technology? Or will they continue to evolve into a full-fledged computing platform and ecosystem that connects users with a community of software and hardware entrepreneurs?

Interestingly, more so than almost any of its competitors, Samsung has a large amount of existing users that could be connected to valuable health solutions. If Samsung pulls this off, they have an opportunity to start the network effects that will eventually lead to a winner-takes-all outcome. [tweetable]Will Samsung seize the day in IoT and create the next dominant computing platform?[/tweetable]

What do you think?

The cross-platform platform: Facebook’s developer strategy

When Facebook was first listed on the stock exchange in 2012, investors were concerned. Had the company missed the mobile wave? 5 years after the launch of the iPhone, most of Facebook’s revenues still came from desktop. Zuckerberg’s team recovered. Today mobile already represents 60% of revenues, and Facebook is about to double down. Apps will become a central part of the social network’s monetisation of mobile. Stijn Schuermans shines a light on Facebook’s new mobile developer strategy.

VM_OSWars

Two years ago we wrote that Facebook was a prime candidate to become the leader of the mobile web; the one who would take care of the missing platform ingredients (reach, discovery, monetization). It should come as no surprise then that over the past year Facebook has shown a renewed focus on helping developers to build – grow – monetize their apps across all mobile platforms. Zuckerberg himself called it the cross-platform platform in his keynote speech on f8. We couldn’t have said it better ourselves.

facebook-graph

The mobile platforms of Apple and Google became so successful because of the large amount of apps that they drew in. For developers, however, this meant heavy competition, few opportunities to stick out and a difficult environment to build a business on. [tweetable]Facebook now positions itself as the developer’s partner that helps to de-commoditize apps.[/tweetable] Facebook can lure mobile apps to its own camp by enabling developers to compete better. Apps will depend on Android and iOS to become available on the majority of handsets, and on Facebook to reach users, get discovered and make money.

Three aspects of Facebook’s strategy warrant a closer look.

Facebook builds a Mega-SDK

Facebook knows developers very well – hacker culture is deeply embedded in the company’s DNA. [tweetable]Facebook is now extending that developer DNA beyond company boundaries[/tweetable], just like Amazon has expanded its cloud operations DNA outside of the company by commercializing its Amazon Web Services (AWS). “Unlike their past developer efforts, which were all about pulling content onto Facebook, this year was about pushing Facebook’s infrastructure out into all kinds of mobile apps”, as Ben Thompson put it. It is a very natural way to empathise and connect with the developers who will build complements to Facebook and Amazon’s core businesses.

How is Facebook going to entice mobile developers? By building one of the first true Mega SDKs. [tweetable]As we predicted last July, Facebook’s Mega SDK will be built around app marketing services[/tweetable]:

  • analytics (relevant acquisitions include Parse, Monoidics, Little Eye Labs, Airlock)
  • promotion (more than 350 million app downloads through mobile app ads to date)
  • re-engagement (Engagement Ads were announced at f8)
  • monetization (the new Audience Network)

Half a dozen acquisitions in the past year, new products and a new developer incentive program (FbStart) all say that mobile developers are becoming incredibly important to Facebook. Although we have to stay careful of course: Mike Mace correctly points out that Facebook in the past has shown predatory behavior (incorporating 3rd party apps into the core product) and neglect for developers.

Digital identity is Facebook’s essence

Facebook’s new anonymous login and privacy features are not just about soothing the privacy pundits and the company’s most vocal users. They point to a deeper reality: digital identity is at the core of everything Facebook does.

[tweetable]Facebooks needs developers to make the Facebook digital identity ubiquitous across web and mobile[/tweetable]. The social network giant does that by reducing sign-up friction on the user side (hopefully also making developers more comfortable with integrating Facebook login). Social login was also a main feature of Parse. Several other highlights at the f8 conference (Send to Mobile, the mobile Like button, even Applinks) make most sense when viewing them as ways to increase the value of a Facebook login relative to a proprietary identity, another social login provider, or no identity at all.

[tweetable]Why this focus on identity? Because it’s crucial for Facebook’s survival[/tweetable]. A study from early 2014 claims that Facebook is about to lose 80% of its users, drawing a parallel with infectious diseases that spread, then flare out. Whether or not that comparison holds water, identity is a powerful antidote to this scenario. If users don’t just use Facebook as their social network, but also to access scores of unrelated services, then it will be hard for users to drop Facebook entirely. The company will still have to work hard to keep users active and engaged, but it will have an opportunity to try.

And, not to forget, Facebook gains a treasure trove of user behavior data that will reach far beyond its own services.

It was no accident that identity was the first item on the “cross-platform platform” list in the graph above, before social. On the web, Facebook also accounts for more than half of all social logins. It fully intends to achieve the same in mobile. The company’s future depends on it.

Facebook wants to become “Google for mobile”

Facebook and Google are mortal enemies, because they have the exact same business model.

  1. Create value for users by developing a score of valuable services (most of them free to use), and enlist developers to create thousands more.
  2. Deliver that value across all digital devices; on the web and on mobile.
  3. Capture value by selling user reach, engagement and hyper-targeting to advertisers.

It is no wonder then that there are many similarities between both companies. Facebook is taking that similarity to the next level with its new products.

The Audience Network is the AdMob of Facebook. It aims to become the key competitor for Google in mobile advertising.

But the boldest move is Applinks. [tweetable]In the most optimistic case, Applinks will allow Facebook to build the PageRank of mobile[/tweetable], a head-on attack on its arch rival. (Facebook has already kindly offered to host an index of all applinks.) At worst, Applinks can substantially boost Facebook’s app install business (CPI) through affiliate marketing schemes, earning revenue on each referral. That supports the Mega SDK for developers as well as Facebook’s own income statement.

Developer Economics: Ecosystem wars drawing to a close

Welcome to the brand new Developer Economics report! Now in its fourth year and 6th edition, the latest Developer Economics survey reached over 7,000+ developers across 127 countries, setting new standards in developer research.

DNAapps

Get your free copy here and read about the movers and shakers in the app economy. Dive deep into our rich dataset and discover how developers select and prioritise platforms, which developer tools they use and how their choices translate to revenues.

As always, we have a lot more data available so get in touch (moredata@visionmobile.com) to get the data you need if you can’t find it in the report. Continue reading Developer Economics: Ecosystem wars drawing to a close

The Language of Talking to Developers: The Importance of Outcome-Based Segmentation

Why outcome-based segmentation should be the cornerstone of developer outreach strategies. VisionMobile’s Data and Operations Manager, Christina Voskoglou, explains why everyone running a developer program should focus on outcome-based segmentation and not technologies, demographics and platforms.

Blog006_Final_Web

00 Shooting the duck

Two statisticians were hunting for ducks by a creek. Spotting one taking off behind a bush both hunters fired simultaneously: The first man’s shot fell 1 meter too low while his friend’s shot flew 1 meter too high. Thrilled, they dropped their rifles and started congratulating each other, hopping about, happily chanting: “We got it on average, we got it on average!”. The duck, even happier than the statisticians, had of course in the meanwhile flown away to safety.

This is a lesson on how working with averages is a sure-fire strategy to miss your targets. [tweetable]There is no average person. And there’s no average developer[/tweetable]. Continue reading The Language of Talking to Developers: The Importance of Outcome-Based Segmentation

App trade: a global opportunity

As we launch our new Developer Economics survey [UPDATE: Survey now closed – results out Jan 2014], Senior Analyst Andreas Pappas quantifies the international dimension of the app economy to visualise app trade routes. With barriers to international expansion disappearing, today’s app economy knows no borders. But almost 50% of developers are not yet crossing those borders.

VM87_AppsTrade

One of the things that make app development attractive to developers is the relatively low effort involved in selling apps across international borders, compared to other forms of international trade. The low barriers to selling apps internationally make app development attractive even in regions where smartphone penetration and app consumption has yet to reach a level that can effectively support local app development. This is the case in Asian countries with smartphone penetration below 20%, compared to over 50% in Western Europe. To some extent, app development is even more attractive in Asian regions, as labour and other costs are lower, compared to western app economies. Continue reading App trade: a global opportunity

Infographic – Developer Economics Q3 2013 – State of the Developer Nation

As we’re about to launch the latest Developer Economics survey [UPDATE: we’ve launched the new survey – you can take it here!], we’d like to present you with an infographic with some key stats and figures from the latest, Q3 project, to whet your appetite. This infographic holds just a sample of the dozens of insights from the Developer Economics Q3 2013 report ([vm_form_download link_text=’full report available for free download’ product_id=’4062′]), tracking the state of mobile ecosystems, developer mindshare, monetisation trends, revenue models and developer tools.

Insights from this infographic:
– Android and iOS lead in terms of mindshare, HTML5 comes third: 71% of mobile developers use Android, 57% use iOS, 52% use HTML5
– Most developers go straight to the browser: The largest share (38%) of HTML5 developers develop mobile websites with another 23% developing mobile apps
– There are more iOS developers also using Android than vice-versa: 69% of iOS developers use Android, but just 40% of Android developers use iOS as their second choice, just ahead of HTML5 mobile (29%)
– iOS leads in average monthly revenues – but Android is closing the gap: At $5,200 per developer per month on average, iOS continues to be the most revenue-generating platform for developers, ahead of Android by a margin of 10%
– The global app economy was worth $ 53Bn in 2012, and expected to rise to $ 68Bn in 2013: The mobile segment corresponds to 12.6% of the global developer population. In other words, 1 in 8 software developers is involved in mobile development in 2013
– Creativity (53%) and the fun of building an app (40%) are the top motivators for developers

Can’t wait for more Developer Economics? Our new survey is just around the bend [UPADTE: new survey is live]- stay tuned and take the survey (if you’re a developer), or help spread the word (if you’re not)! For the moment, enjoy this great, new infographic!

DEQ313_600