Building Native Apps with SAP Mobile Platform – Enablement Resources
Developing Native Mobile Apps with SMP
The SDK of the SAP Mobile Platform provides you with tools that streamline the development. One of the most common types are Native Apps: mobile apps developed specifically for one device operating system.
Native apps typically perform better than other application types and provide full access to a device’s hardware.
They are often used for consumer facing apps – when branding and customer satisfaction are of highest priority. As a draw back, native apps have to be re-written for different device technologies, therefore can come at a higher cost.
Our harmonized OData SDK provides an open and flexible framework for native OData application development for both online and offline applications for the most popular devices OS’s: Android, iOS and Windows.
The name “Harmonized” comes from the concept that you can use very similar APIs across different platforms for native and cross-platfom apps, which run on either on-premise version or HANA Cloud Platform Mobile Services. We have different programming languages but ideally we want to use the very similar APIs – hence “harmonized”!
Native Apps by Operating System
As always, the Documentation (SMP 3.0 SDK SP12 for iOS) is a great start to get going.
Online APIs for iOS Apps
Offline APIs for iOS Apps
Stan Stadelman has authored a number of technical blogs, one focusing on iOS:
1. In Introduction to HttpConversationManager, and SAML2 Auth in Mobile SDK, Stan describes how this provides a flexible framework for enterprise authentication in your apps.
With SMP 3.0 SDK SP5, we have introduced the SDK for Windows apps. Check out the detailed SDK SP5 blog by Product Manager Kiran Karunakaran. You would also find Documentation (SMP 3.0 SDK SP12 for Windows) very useful to read.
Also, check out the blog series by Milton Chandradas from the Technology RIG team.
Introduction to Developing Windows Apps with SMP
Alongside iOS and Windows, the SAP Mobile Platform supports development of native Android Apps with its SDK.
In December 2014, Google launched Android Studio, Google’s official Integrated Development Environment (IDE) based on IntelliJ and it discontinued the Android Developer Tools (ADT) plugin for Eclipse, which means it’s time to leave eclipse behind. Check this blog if you are interested in Migrating Eclipse Based Projects to Android Studio
On-boarding Users onto the SAP Mobile Platform
Before any communication with the SAP backend systems can take place, a mobile app needs to on-board users onto SMP.
You can check the next post for a detailed description of the methods available to registrate in the SMP:
We support two ways of doing so, and Claudia describes them in her How-To Guides:
These How-To Guides by Claudia show the step-by-step procedure on how to code an Android app to consume OData services. The guides use the Flight sample service available in all SAP Gateway installation.
Push Notifications: The SAP Mobile Platform provides native push notification support for major enterprise mobile platforms. This guide discusses enabling push notifications using SAP Mobile Platform, focusing on the specifics of the Android device platform and the Google Cloud Messaging (GCM) service. This guide uses new AppSettings API available to download and upload application setting from and to the Mobile platform.
Using the SAP Mobile Platform gives you a number of features, one being ‘supportability’. Claudia has authored two How-To Guides on this topic. Make sure to also check the webinar recording by John Polus, where he explains how Solution Manager can be used for system monitoring.
Webinar: On-boarding & Developing Online and Offline Apps
Check the webinar recording below to get started with the SMP 3.0 SDK SP05+ for Android
As time allows, we will convert eclipse-based projects into Android Studio based project. The following guides represent those ones that have been already replaced.
|Brought to you by the SAP Technology RIG and the SAP Mobile Platform SDK Development Team|