Time is running out! Call for Code submissions due July 29 ›
by Thejaswini Ramachandra, Sahdev Zala | Published July 2, 2019
Businesses today realize that mobile apps are a key interaction channel. Users download only the top-rated, engaging mobile apps, and developers strive to build such an engaging app experience.
An engaging mobile app running on the user’s device is only the visible part of an iceberg. The intelligence of this mobile app lies in the backend which processes all the user interactions. The mobile backend server provides capabilities like user management, push notification, app management, app insights, secure backend integration, and more, which are basic aspects of any mobile app.
It can be time consuming for developers to develop these capabilities for every mobile app, while also building the front-end user experience, which is the most critical aspect for mobile app adoption. Mobile backend service providers offer these backend capabilities which can be consumed by the front-end application via API’s and SDK’s. Developers prefer to focus on writing code to build the best user experience, while leaning on cloud providers to deliver backend capabilities.
The popular terminology used to refer to these offerings are “Mobile Backend as a service” (MBaaS) or “Backend as a service” (BaaS). This backend server further interfaces with business logic layer written with microservices patterns and consumes high value services such as cognitive and analytics REST API’s. Refer to the Mobile Reference Architecture for details.
A mobile backend typically offers a diverse set of features that can be leveraged based on the application needs:
IBM Mobile Foundation, which offers many of these capabilities, is a scalable, secure mobile backend offering with simplified integration to other IBM Cloud services.
Push notifications are a great way to engage app users and offer them “mobile moments.” Today, mobile backends usually support sending rich content including title, subtitle, launch image, style, and more, as well as a picture notification or a silent notification.
To send Push notifications to mobile apps, you need to go through a device registration cycle and leverage a mediator provided by the Mobile OS vendor. Your backend cannot directly push messages to the mobile app. Firebase Cloud Messaging (FCM) for Android and Apple Push Notification Service (APNS) for iOS are the mediators that help send notification messages to mobile devices.
In certain countries like China, you have to use the country specific notification provider like Baidu. Most backend vendors offer multi-channel notifications to mobile, web, and progressive web apps. IBM provides a Push Notifications service that lets you send and manage mobile and web push notifications using a UI, client SDK, or simple REST APIs.
Mobile security is multifold requiring developers to protect data on the device, over the air, and on the server. Mobile backends typically provide data encryption and protection on the device and also protection against malicious apps connecting to the server.
Some backend providers also offer additional capabilities like protection against man-in-the-middle attacks, prevention of jail-broken devices from accessing the backend, limiting of single user per device for compliance needs, step up authentication support, and more.
In today’s agile world app, updates to mobile apps are released more often, and mobile backends must provide capabilities for administrators or developers to manage app version updates, remotely disable an app on user device.
Quite often the developer might want to test a new feature with a small subset of users to gather feedback instead to releasing the feature to the full set of users. There is also a requirement to enable a particular feature on a particular date, or an ability to turn that feature off based on some business use case.
Many cloud providers provide this capability. They also provide the capability to measure the usage of that feature as well as sophisticated parameters to define subset of users to whom the feature should be made available
Offline availability is a key aspect for many mobile apps. Caching catalogs for offline browsing is a common use case. Mobile backends provide ways to securely cache structured, unstructured, or binary data on the device to support multiple offline use cases. This data needs to be synchronized with the main system of record (SoR) either when modified locally (upstream synch) or modified in the SoR(Downstream synch.). This storage on the device also has to be secure so no one can get access to the data when the device is stolen or infected.
This capability is offered by Cloud providers and is accessed by means of installing an SDK in your app code. Along with data synch capabilities, often there is a need to store the data in a SQL or NoSQL format instead of synching it to a SoR. These data storage on Cloud capabilities are also integrated with Synch SDk’s. The GraphQL framework is emerging as the new technology of choice for providing this capability.
After the app is distributed through internal or external app stores, it will be installed on a matrix of devices across models and OS versions. The admin or developer would like to obtain insights on the number of downloads, the user journey, and app crashes (if any occurred).
Most mobile backend providers offer the capability to collect useful insights about the user and their app usage.
Most – if not all – apps need a way to register and identify a user. This involves user authentication using social login or a custom user store. This login also often needs registering with on-device biometric authentication and not just typing in a username and password. Most cloud providers provide user registration, authentication and authorization capabilities. Mobile backend providers also offer integration with user registries like LDAP, so that organizations can leverage existing user registries to authenticate users. They also support OAuth and integrate with internal identity and access management systems. IBM provides the APP ID service which offers these capabilities.
Quite often – particularly in the enterprise use cases there is a need to connect to a system of Record (SoR) or be able to write a custom logic closer to the SoR before it is sent to the Mobile apps. Patterns like the Backend for Frontend (BFF) microservices can be written in Swift, Node.js, Java or any other convenient language. All cloud providers provide a way to deploy these microservices. Some vendors also provide a “Adapter” capability that adds a security framework around the access to these microservices and an access to them using an SDK that can be added to the mobile app.
Mobile real estate doesn’t afford the user with the luxury of showcasing large data similar to what web sites can display. Mobile backends optimize throughput and provide data mash up capabilities, such that precious network resources can be used to transfer only the required amount of data with most of the processing being performed on the server side. JSON format is most widely used for data transfer, although XML and YAML options are sometimes used.
Mobile devices are getting powerful enough to execute Machine learning models on the device itself. This provides for enhanced experiences to be added to the mobile app without having to wait for a backend service to respond back with the analysis on an image or voice snippet. Portable model formats like TensorFlow Lite by Google and CoreML by Apple started for their own respective devices but are providing support for the other OS as well. However, you need a backend capability to train these models and manage the distribution of these models to the devices. Many cloud vendors provide Machine Learning services that can be trained by a data scientist or specialized ML training services like Image identification. The ability to augment the mobile app with a chatbot is another latest addition of AI capability that some mobile backend vendors now offer.
The cloud computing model enables on-demand access, and any app being built in today’s world should leverage the power of cloud computing architectures. A mobile backend hosted on the cloud caters to additional nonfunctional requirements like scalability, reliability, performance, load balancing, and security, all of which are typically managed and orchestrated by a service provider. Cloud-based mobile backends also offer easy integration with DevOps offerings for continuous delivery of the mobile backend app. Cloud-based mobile backends can also take advantage of offerings with regional availability.
All major cloud providers (IBM, Google, Amazon, Microsoft) offer specific design patterns (app frameworks) that can serve as a mobile application backend. Some vendors offer a single mobile backend with a multitude of capabilities while others offer “a la carte” offering capabilities with a variety of pricing models. Most cloud providers include some form of freemium model, where core features are offered free of charge up to a certain usage limit. It is easy to create and launch an app with the free tier and then scale up to a paid tier to onboard additional customers.
You can get started building secure, scalable, and engaging multiplatform mobile apps using the IBM Cloud Mobile Starter Kits.
Choosing the right technology to build your frontend mobile apps is critical. A continuum of technologies is available to choose from, and various factors determine the platform of choice. You can read more about choosing a frontend mobile platform this IBM Developer article, “Deciding between native and cross-platform mobile frontend programming frameworks.”
After you make the choice of mobile frontend technology, you can get started with mobile backend on Cloud and build 5-star rated engaging mobile apps. Mobile backend providers offer SDK’s for many popular frontend technologies like Android, iOS, Cordova, Ionic, React Native, and Xamarin. They also provide REST API’s that can be leveraged from the frontend applications. Many vendors offer low-code drag-and-drop tools to quickly wire up a mobile frontend interface which can be leveraged as a starting point. You can read more about the programming languages, SDKs, and frameworks for full-stack mobile development in this IBM Developer article, “Choosing the best programming language for mobile app development.”
This article highlights the need for mobile backend, with the sneak peek of core capabilities offered by mobile backend providers. It also makes a good case for cloud based mobile backends. Mobile backend vendors are now evolving the mobile backends to support many channels (web, voice, chat) while providing a seamless omnichannel experience with user at the center and the channels coming together to provide a holistic user experience.
This article explores the features of full-stack mobile development environments and covers several core native and hybrid mobile alternatives and…
Discover the programming languages, frameworks, or SDKs you can use to create native, cross-platform, or web-based mobile apps.
Understand the tradeoffs and development considerations for native and cross-platform mobile development frameworks.
To design a full-stack mobile app, you must consider the total user experience of the app – from the graphical…
Get the Code »
Back to top