Are you using the right app revenue model?
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.
Cross-Platform Tool Trends - Freemium & Flexible
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?
How Much Is An Active User Worth?
App store analytics providers have been telling us that almost all of the growth in app revenues in the last year has been through in-app purchases. However is that just because the model has become more popular? Or because revenue has been concentrating at the top of the market, where the strategy is very popular (particularly in free-to-play games)? Probably...
Cross-Platform Tools - Does it pay to use them?
In our January 2013 Developer Economics Report, we revealed that multi-platform developers are better off. Our survey data also reveals, rather unsurprisingly, that users of cross-platform tools (CPTs) target more platforms than those building separate apps for each platform. Of those interested in making money, users of CPTs target 4.33 platforms (3.1 mobile platforms) on average vs 3.46 platforms (2.57 mobile) for those building separate apps. We also know that...
HTML5 vs Native - What are the tradeoffs?
In our latest developer survey we asked developers who use or plan to adopt HTML5 why they do so and also what the technology needs to compete with native alternatives. The results show a tradeoff of increased portability and lower development cost against capability, in the form of reduced API access and a poorer development environment. In this scenario, the key to success with web technologies is taking advantage of their strengths in areas where their weaknesses are less of a handicap.
The Costs of App Security
The security features of an app are often ignored in the rush to get a new product to market. We naturally tend to focus more on what an app should do, rather than what it shouldn’t. Making sure that an app doesn’t have security flaws is a difficult and potentially expensive process. There are...
Developer Economics 2013 Survey: iOS vs Android shoot-out
We asked developers to pick the top platform, among all platforms they have used or are planning to use, on a number of different aspects of mobile development such as discovery, learning curve and monetisation. We then compared how iOS and Android fare against each other, based on the opinions of developers using both platforms. Find out which platform came out on top.
How Much Time Could You Save With Backend-as-a-Service?
Backend-as-a-Service (Baas) provider Kinvey published an interesting infographic on the average time taken to build an iOS or Android app (with a backend service) this week. The data comes from a survey of 100 developers with their estimates averaged. For apps with relatively complex backend requirements as featured in the survey, our simple analysis suggests developers could save 45% of the effort required to ship a Minimum Viable Product by using a BaaS.
Cross-Platform Tools - Functionality and Trade-offs
Cross-platform tools (CPTs) are a class of developer tool that aim to enable a single implementation of application functionality to run across multiple platforms. If that definition seems very broad it’s because the category covers a wide range of use cases, technology approaches and forms of app deployment. In our analysis of this sector from February 2012 we identified over 100 tools across three forms of app deployment (native vs. web vs. hybrid) and five different technology approaches