Use the push feature to push updates from the back-end data source to applications that are running on mobile devices.
You can use SAP Mobile Platform to manage push for individual applications that use native notifications.
Developers enable native push notification in the application code, and link the certificate with the mobile application at build time. Users download the application from a market place, such as Apple App Store, Google Play, or similar service, and, when a change occurs in the back end, it sends a push notification to mobile applications on devices with push enabled.
For native mobile applications, the platform manages the certificates, tokens, and push notifications for individual applications. When changes occur, the back end sends push notifications to mobile applications on devices that are push enabled.
Custom Push Provider
The custom push provider enables you to configure applications to receive push notifications via a private push vendor. For example, for an application running on Android, you may want to replace the GCM push service for a local vendor service. Configure the custom push provider for specific device types.
View push notification statistics for push-enabled apps from Push Statistics. You can see notification details, notifications by applications, and notifications by operating system.
Capabilities-based Push Support
Capabilities-based push enables a back-end to trigger a push to applications that provide a certain capability. Developers configure application connections to handle capabilities using the REST API (see REST API Application Development Overview). Devices send capability type information during registration or update. SAP Mobile Platform maintains the mapping between capabilities and applications.
Device-type (form factor) Support
Configuration of Capabilities
Application capabilities are part of the central application connection configuration. Similar to how the administrator controls some device capabilities from the server through feature policies, users control some application capabilities from the device. Device capabilities are controlled by the application and sent to the server. The capabilities are exchanged between the mobile app as part of the registration and settings exchange.
Through that mechanism, the mobile app can also override default capabilities. This gives users more control, enabling them to turn off certain capabilities for a mobile app instance, which translates into turning off native push notifications for a certain action into a particular application. Push can still be offered, but at the capability level, rather than individual application level.