whitepaper: mobile Backend as a Service (BaaS) explained
2
Backend-as-a-Service, BaaS, explained 1 BACKEND AS A SERVICE (BAAS) EXPLAINED The concept of a Backend-as-a-Service (BaaS), or cloud based mobile backend, is simple. Most application developers (web or mobile) require a core set of features in their app, for instance user management, push notifications, integration with Facebook, Google+ etc., and stable and effective data transfer on an unreliable data connection to the central data storage. The features must also be platform transparent so that the developer can release their apps on, for instance, iPhone, Android and web, offering the same end-user features. These backend features are the “bread and butter” of BaaS and included in the service from most BaaS providers. A rule of thumb says that those repetitive tasks take about 50% of overall app development time and cost. Complex and tedious tasks reduced to a few lines of code so that developers instead can focus their time and energy on the app itself. Most BaaS providers offer: Simplified implementation through an SDK (software development kit) which provides a way to reduce the code required to implement all the features • Any platform, anywhere. Most BaaS companies make it easy to implement and deploy backend features to multiple mobile and web platforms, through libraries for iOS, Android, JavaScript, etc. • Scalability to handle the challenges of success and rapid growth of users • High level of security • Application management with analytics dashboard, something rarely developed within a single app project The global BaaS market is estimated to grow from $216.5 million in 2012 to $7.7 billion in 2017. This represents a compound annual growth rate (CAGR) of 104% from 2012 to 2017. MarketsandMarkets October 17, 2012
description
An overview of the Backend as a Service concept from the PingPal point of view.
Transcript of whitepaper: mobile Backend as a Service (BaaS) explained
Backend-as-a-Service, BaaS, explained 1
BACKEND AS A SERVICE (BAAS)
EXPLAINED
The concept of a Backend-as-a-Service (BaaS), or cloud based mobile backend, is simple. Most application developers (web or mobile) require a core set of features in their app, for instance user management, push notifications, integration with Facebook, Google+ etc., and stable and effective data transfer on an unreliable data connection to the central data storage. The features must also be platform transparent so that the developer can release their apps on, for instance, iPhone, Android and web, offering the same end-user features.
These backend features are the “bread and butter” of BaaS and included in the service from most BaaS providers.
A rule of thumb says that those repetitive tasks take about 50% of overall app development time and cost. Complex and tedious tasks reduced to a few lines of code so that developers instead can focus their time and energy on the app itself.
Most BaaS providers offer:
Simplified implementation through an SDK (software development kit) which provides a way to reduce the code required to implement all the features
• Any platform, anywhere. Most BaaS companies make it easy to implement and deploy backend features to multiple mobile and web platforms, through libraries for iOS, Android, JavaScript, etc.
• Scalability to handle the challenges of success and rapid growth of users • High level of security • Application management with analytics dashboard, something rarely developed within a single app
project
The global BaaS market is estimated to grow from $216.5 million in 2012 to $7.7 billion in 2017. This represents a compound annual growth rate (CAGR) of 104% from 2012 to 2017.
MarketsandMarkets October 17, 2012
Backend-as-a-Service, BaaS, explained 2
THE SPECIALIZED BAAS
There are also a few emerging BaaS that have a specific niche focus, as PingPal. Besides offering the standard features we have extended high level feature modules targeting more specific and complex needs for specific app types.
PingPal focus on providing positioning, map provisioning and communication functionality that is optimized for the outdoor end-user scenario with high risk of poor mobile data network coverage. Most PingPal features only require 2G/GPRS networks while still maintaining full functionality.
Based on the same rule of thumb mentioned above the savings in using a niche BaaS is much higher, 70-80%. Of course if the app requires some or all of the features PingPal provide.
With the rapid development of BaaS platforms the future of mobile app development can only get more cost effective, simpler and reliable.
COULD YOU BUILD YOUR BACKEND ALL BY YOURSELF?
Sure! All you have to do is:
• select, install and configure a technology stack • write, test, optimize and maintain the backend code over the whole app life span • connect third-party cloud APIs, manage new features and ensure nothing breaks when the APIs
change • be ready to wake up in the middle of the night to scale servers
