Publish any data into a “wallet” or “passbook” style application with mobile card kit. Mobilize data for both iOS and Android apps.
More information
Reduce app development cost by leveraging drag & drop simplicity of no code tool.
Mobile Development Kit (MDK) is a feature in SAP Mobile Services, it is a metadata-driven tool that allows users to customize native SAP applications, as well as rapidly create new native mobile applications. MDK uses SAP Web IDE Full-Stack and the SAP Business Technology Platform (BTP) to enable you to customize, deploy, and manage mobile apps in the cloud.
Reinvent how work gets done by creating rich new native business app.
SAP BTP SDK for iOS enables you to quickly develop your own native apps, with Swift programming language. Along with SAP Fiori for iOS, which includes reusable design components, the SDK also allows you to tap into the services and functions available in the SAP BTP so you can build beautiful intuitive native applications.
Reinvent how work gets done by creating rich new native business apps.
SAP BTP SDK for Android enables you to quickly develop your own native apps using Android Studio and your preferred programming language. Along with SAP Fiori for Android, which brings the Fiori Design to the Android platform, the SDK also allows you to tap into the services and functions available in the SAP BTP so you can build powerful and elegant native applications.
Build end-to-end mobile solutions
Mobile Back-end Tools (MBT) is a part of the SAP Mobile Services that allows developers to model an OData service and generate a Java EE web application. This generated Java application can then be deployed to the SAP BTP which will act as a host for the OData service. This OData service manages the tables and other SQL artifacts within your target database.
Quickly mobilize existing ABAP transactions
Mobile Transaction Bridge is a tool which helps SAP customers to easily and quickly mobilize SAP GUI transactions by using screen recording to generate OData service which then can be consumed by the low code tooling of our MDK, native apps and mobile cards.
More information
Taxes calculated during checkout
SAP Mobile Services, standard edition
In the Standard edition, billing is by named users. Named users are individuals authorized to access the Cloud Service. Users are employees of Customer or Customer’s Affiliates, or users of business partners.
Unit = Users
use case: B2B, B2E scenarios
Minimum users: 25 named users / month
Includes: Neo (preview landscape available) and Cloud Foundry Environment
Taxes calculated during checkout
SAP Mobile Services, consumer edition
In the Consumer edition, billing is by active users. An active user is an individual user of a Platform Application that connects to the Cloud Service at least once during any rolling one-month period.
Unit = Block of 50,000 users
use case: B2C scenarios
Includes: Neo (preview landscape available) and Cloud Foundry Environment
SAP Mobile Technologies Community
Learn more from our community of SAP Mobile experts .
Go there now
Have a question?
Interested in buying SAP Mobile Services product but still have some questions?
Contact us now
In order to use SAP Mobile Services, you must first have SAP BTP bandwidth.
In order to use SAP Mobile Services, you must first have SAP Application Runtime service.