- About this guide
- BlackBerry Dynamics background
- BlackBerry Dynamics API reference
- FIPS 140-2 compliance
- Easy Activation
- Securing cut-copy-paste on devices (Data Leakage Prevention, or DLP)
- Shared Services Framework
- Support for fingerprint authentication
- Support for Face ID
- Support for certificates
- Support for the "Do not require password" setting
- Bypassing the App Lock screen
- BlackBerry Dynamics contributor code on GitHub
- Supported languages
- Requirements
- BlackBerry Dynamics software versions
- Compatibility with earlier releases
- Software requirements
- BlackBerry Dynamics entitlement ID and version
- Requirements: Frameworks and libraries
- Requirement: URL scheme
- Required build-time declarations: URL type
- Using NSURLSystem for KCD
- GDAssets.bundle required in build phase
- Compatibility with the BlackBerry Dynamics Launcher Library
- App UI restrictions
- Supported and unsupported features on iOS
- Link for FIPS in Objective-C or C++
- Steps to get started with the BlackBerry Dynamics SDK
- Programming with the BlackBerry Dynamics SDK and BlackBerry Enterprise Mobility Server services
- Sample apps in Objective-C
- BlackBerry Dynamics and the Swift programming language
- Testing and troubleshooting
- Readying your app for deployment: server setup
- Details of support for client certificates
App UI restrictions
The
BlackBerry Dynamics Runtime
monitors the app UI to enforce a number of enterprise security policies configured in BlackBerry UEM
or
standalone Good Control
. For example,
a security policy may require the user to enter a password when the app transitions from the
background to the foreground, or may lock the app UI after a certain period of inactivity.The app UI must follow certain restrictions to enable monitoring by the
BlackBerry Dynamics Runtime
. For a complete explanation
of the restrictions, open the BlackBerry Dynamics SDK API Reference for your platform and see the
section “Application User Interface Restrictions” in the appendix.