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?
Backend-as-a-Service Shootout (the best alternatives to Parse?)
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.
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