Show TOC

Android ApplicationsLocate this document in the navigation structure

Develop an OData online, occasionally offline, or offline application.

NoteThe following image contains links to more information.
Develop an OData online, occasionally offline, or offline application. Set up your Android environment for Native OData app development. Configure the application in the SAP Mobile Platform Server Management Cockpit or HANA Cloud Platform Mobile Services Cockpit. MAF logon components implement user onboarding workflows. Client Hub is a native application a user installs on the device that allows multiple business applications to share common credentials enabling an SSO-style behavior. The Client Hub, integrated with Logon Manager, simplifies user onboarding and configuration to enable easier and faster enterprise-wide deployments. Client Hub is an additional layer of management on top of the shared keychain, and allows end users to control which applications are using their credentials. The Client Hub reduces the effort required by the end user to manage multiple passwords for mobile applications and improves the user experience. Client Hub supports both OData and Hybrid (Kapsel) applications. APIs for SAML and Mobile Place. The SAP Mobile Platform SDK provides a set of features and APIs (collectively referred to as supportability) that captures errors, traces and logs events, then uploads this information to the SAP Mobile Platform Server, where it can be analyzed from the cockpit. The Conversation Manager (HttpConversation library) facilitates sending and receiving HTTP requests and responses between an Android app and server, and is built on top of the and APIs, which are provided as part of the Android system. The Supportability API logs messages and supports end-to-end tracing through the enterprise system. Understand how to develop a native Android application that uses an online OData store. Understand how to develop a native iOS, Android, or Windows application that uses an offline OData store. Understand how to implement a "technical cache" to extend native Odata applications that use an online OData store for read requests in environments where the application is occasionally offline due to network issues. CUD requests do not go through the cache. The SAP Mobile Platform SDK for Android provides three APIs for accessing and manipulating an OData source. MAF reusable controls allow you to use native Android UI controls (such as buttons and labels) that display a default SAP style, from a prebuilt library. You can skin these components at runtime to match customer branding, without recompiling the source code. MAF also contains a set of complex controls, such as the calendar, the tree view, and locale-aware controls. These complex controls, which provide additional runtime skinning capabilities, are built from the simple MAF controls. The Extensibility Framework is an SDK for Android applications, providing to developers the ability to add or replace screens or subviews, change navigation patters, update the data model, add custom actions, and so on. You can use it when developing new applications, but you can also extend existing applications with little effort; you need not recompile and redistribute the apps. The Mobile Application Workbench (MAW) lets you  customize mobile applications that you build using Mobile Application Framework (MAF). You can change SAP-supplied configurations (also called application metadata), package the changes, and deploy them to the SAP Mobile Platform. Packages are provisioned to mobile applications that have subscribed to change notifications. Run the Android application on a real device or on an emulator. Publish an Android application to an app marketplace such as Google Play, or make it available for download from the SAP application store. Once an application is deployed to a device, debug problems by analyzing device crash logs and console output. Review information about common problems that arise when working with SAP Mobile Platform SDK.