Consumer apps are the focus for all the excitement and media attention in the industry. Enterprise software is dull and boring, right? Not if you care about making money! Besides, what’s so dreary about reinventing the way people work in a mobile and connected world?

“Wait”, I hear you cry, “what about BYOD and the consumerization of IT? Surely the future is all about selling computing tools directly to professionals?” Well the data from our last Developer Economics survey says that future isn’t here yet. In any case, if you’re going to collaborate with colleagues then you all need to be using the same tools, so most of the time the company still has to choose and buy them.

We asked developers which type of customer they primarily targeted from a selection of Consumers, Professionals, Enterprises, Other and Not Sure. Using this data we can compare the fortunes of developers serving each of those audiences.

Although the debate on HTML5 versus native apps seems to be favouring native apps currently, particularly in terms of user experience and performance, average developer revenues tell a very different story. Our survey data shows the mean average revenue for developers who consider HTML5 for mobile devices their primary platform is the highest of all platforms, just over twice that of the next nearest (iOS)*. However, the rewards are very unevenly shared, with the median average revenue for the same developers under half that of their iOS counterparts. Diving into the data we can see significant differences in revenue depending on how mobile apps built with web technologies are delivered to users and the categories they target. Understanding these differences could improve your chances of succeeding with HTML5.

The most popular revenue models appear to be those that are easiest to implement. The developers using them tend to have lower revenues. This may be due to greater competition or it might just be a result of less sophisticated app businesses producing less valuable apps. There are some interesting differences between platforms but subscriptions appear to be a relatively untapped gold mine everywhere, although maybe not for everyone.

As the market temperature for cross-platform tools (CPTs) continues its steep climb into hotter territory, it’s understandable why many feel we are witnessing a mobile fragmentation that is perhaps much larger and more significant than the recent wars waged over the desktop. If this fragmentation tells us anything, it’s that [tweetable]cross-platform tools for mobile development […]

The mobile apps business is maturing and while most of the media attention is still focussed on the latest app store success stories, developers are finding lots of better ways to make revenue with their apps. Considering all revenue sources, which categories of application are generating the most money and what’s the competition like on each platform?

Creating versions of an app for multiple platforms (at least iOS & Android) is an increasingly common requirement. Building and maintaining native code for every platform supported is both difficult and expensive. Cross-Platform Tools (CPTs) offer a solution to this problem by enabling sharing of code across platforms and in many cases a single code base can target multiple platforms. With such significant cost savings available, why don’t all developers use CPTs?

Making money from your app is really difficult. Pricing is intuitively an important part of the potential of any app. Price too high, and you price yourself out of the market, but price too low, and you’re leaving preciously needed money on the table. Michael Jurewitz comes to the rescue! In a five part blog post series, the Apple veteran explains the ins and outs of app pricing, tackling crucial issues like differentiation, pricing power, price elasticity and a practical plan to optimise prices based on your app’s data.

4 out of 5 developers admit that their app doesn’t make enough money to be considered a standalone business. 2 out of 3 doesn’t break even. And yet there is hope.

John Cooper, founder of Pyxis Ventures, shares his personal experiences with promoting apps.

Using a Backend-as-a-Service (BaaS) can reduce development cost and time-to-market. It’s a simple way of getting a highly scalable backend solution without significant upfront investment. In a world where an app that hits the store top charts might gain more than a million new users before you complete your next iteration of development this is worthy of serious consideration.