- What is the BlackBerry Dynamics SDK?
- Requirements and support for platform-specific features
- Software requirements
- Using an entitlement ID and version to uniquely identify a BlackBerry Dynamics app
- FIPS compliance
- Declaring a URL type to support BlackBerry Dynamics features
- App UI restrictions
- Requirements and prerequisites for iOS platform features
- Supported TLS protocols and cipher suites
- Steps to get started with the BlackBerry Dynamics SDK
- Integrating optional features
- Preventing password autofill in the app UI
- Enforcing local compliance actions
- Adding custom policies for your app to the UEM management console
- Adding a custom logo and colors with the branding API
- Using zero sign-on for SaaS services through BlackBerry Enterprise Identity
- Integrating BlackBerry Enterprise Mobility Server services
- Sample apps in Objective-C
- Testing and troubleshooting
- Deploying your BlackBerry Dynamics app
- Deploying certificates to BlackBerry Dynamics apps
App UI restrictions
The
BlackBerry Dynamics Runtime
monitors the app UI to enforce the configuration of enterprise profiles or policies from BlackBerry UEM
or standalone Good Control
. For example, a BlackBerry
Dynamics
profile may require the user to enter a password when the app transitions from the background to the foreground, or it may lock the app UI after a certain period of inactivity.Note that SDK version 6.0 and later supports the use of multiple UIWindow objects. No coding is required to use this feature. The AppKinetics sample app demonstrates support for multiple UIWindow objects.
For a complete explanation of the restrictions and requirements that the app UI must follow, see Application User Interface Restrictions in the API Reference.