onedevatlasBeta
Browse the atlas
AllBTPCAPUI5ABAP
ServiceServicetypeA BTP service you subscribe to and bind, rather than install. It has plans and regions, not versions, and may deliver a product that lives outside the atlas.See every one →What this type is →by SAPby SAPoriginPublished by SAP itself. A visible facet, never an input to a reading — a dormant official plugin reads exactly like a dormant independent one.See every one →

SAP Mobile Services

The SAP BTP service behind native and cross-platform mobile apps over enterprise data: authentication and security policies, offline OData sync, push, MDK app updates and usage reporting.

A mobile app that reads and changes enterprise data needs a server side: authentication, data kept on the device for when there is no network, notifications from the back end, and a way to lock a user or wipe their data. SAP Mobile Services is that server side for apps built with the Mobile Development Kit, the SAP BTP SDK for iOS or the SAP BTP SDK for Android, and it is the channel for mobile development through SAP Build Code. Administrators manage an app's lifecycle in one interface: the authentication type and security policies, push notifications, offline stores kept current through OData synchronisation, locking, wiping and deleting user data, and usage reports. An app built with the Mobile Development Kit is updated without a new code-signing round.

Homepage
Docs

Where it sits

Lives in
BTP/BAIP
Provides
Mobile appsBTPMobile appscapabilityBuilding a native iOS or Android app over business data: onboarding, offline sync against an OData service, device features, and the client that runs on the phone. Distinct from a web app opened in a phone's browser; operating a web app with a finger is [touch operation](capability:ui5-touch-uis).

Who is behind it

SAPSAPOrganisationMaintains this
In the atlas: maintains 137, wrote 14@SAPmaintainer

Before choosing this

Signals

Service plansSome service plans deprecated2 of 8 plans deprecated

The SAP service catalogue marks one or more plans as deprecated. Inspect the affected plans and their replacement guidance before choosing one.

What it declares

Every artifact

Type
Service
Origin
By SAP

As a service

Plans
8
Regions
39
Support component
MOB-CLD-CF-CORMOB-CLD-CF-OPSMOB-CLD-CORMOB-CLD-OPSMOB-FMMOB-FM-SEC

Connections4

Download
SAP Mobile Services connectionsSAP Mobile ServicesPROVIDES→ provides1provides stated The server side of an SAP mobile app: authentication, offline OData sync, push and lifecycle management for apps built with MDK or the SAP BTP SDKs for iOS and Android. SAP Discovery Center — SAP Mobile Services: https://discovery-center.cloud.sap/servicecatalog/api/v1/services/ca798dc0-4b35-4f2b-b66e-3ac225c3359e SAP Discovery Center — SAP Mobile Services: https://discovery-center.cloud.sap/servicecatalog/api/v1/services/ca798dc0-4b35-4f2b-b66e-3ac225c3359e SAP Discovery Center — SAP Mobile Services: https://discovery-center.cloud.sap/servicecatalog/api/v1/services/ca798dc0-4b35-4f2b-b66e-3ac225c3359e SAP Discovery Center — SAP Mobile Services: https://discovery-center.cloud.sap/servicecatalog/api/v1/services/ca798dc0-4b35-4f2b-b66e-3ac225c3359e SAP Discovery Center — SAP Mobile Services: https://discovery-center.cloud.sap/servicecatalog/api/v1/services/ca798dc0-4b35-4f2b-b66e-3ac225c3359e SAP Discovery Center — SAP Mobile Services: https://discovery-center.cloud.sap/servicecatalog/api/v1/services/ca798dc0-4b35-4f2b-b66e-3ac225c3359e SAP Discovery Center — SAP Mobile Services: https://discovery-center.cloud.sap/servicecatalog/api/v1/services/ca798dc0-4b35-4f2b-b66e-3ac225c3359eMobile appsUSED BY← connected from1connected from derived If: push notifications are activated The Android shell registers the device against the Mobile Services push runtime API, and the ABAP class `zcl_test_mobile_push` sends an alert with a deep-link URL to all devices of a user through the backend push API. Through: inverted from its connects edge abap2UI5/mobile-shell — PLAN.md: https://raw.githubusercontent.com/abap2UI5/mobile-shell/main/PLAN.md abap2UI5/mobile-shell — PLAN.md: https://raw.githubusercontent.com/abap2UI5/mobile-shell/main/PLAN.mdabap2UI5 mobile shellif← optionally used by1optionally used by derived If: push notifications are activated Push: the device registers against the Mobile Services push runtime API and the ABAP client sends through its backend push API, which takes Mobile Services credentials beside a Firebase project and an APNs key. Through: inverted from its requires edge abap2UI5/mobile-shell — README: https://github.com/abap2ui5/mobile-shell abap2UI5/mobile-shell — Distribution & hardening: https://raw.githubusercontent.com/abap2UI5/mobile-shell/main/docs/DISTRIBUTION.mdabap2UI5 mobile shellif← used by1used by derived managing and consuming Agentry services, which do not run without the mobile service for development and operations Through: inverted from its requires edge SAP Discovery Center — Agentry: https://discovery-center.cloud.sap/servicecatalog/api/v1/services/2064dea3-c038-4173-b52c-9cc405517a5bAgentry

Others providing3

Compare all 4 on the Mobile apps page →
Mobile apps
  1. abap2UI5 mobile shellNative iOS and Android shell for one abap2UI5 endpointfrom ABAP
  2. AgentryBTP service for building and running Agentry mobile appsfrom BTP/BAIP
  3. SAP Build AppsLow-code platform for web and native mobile appsfrom BTP/BAIP

Details

Sources1
Added by handdiscovered herechecked

Sources are graph entities: the same page may back several entries, and an unreachable source flags every row that rests on it.

Compatibility and provenance
discovered viaAdded by hand
first seen in the atlas
ecosystem and domainbtp, ui-and-frontend-bridge
History in the atlas1
  1. First seen.
For your agent
Ref
artifact:btp-mobile-services
JSON
/artifacts/btp-mobile-services.json
MCP
Connecting an agent