- 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 certificates
- Support for the "Do not require password" setting
- Bypassing the App Lock screen
- BlackBerry Dynamics contributor code on GitHub
- Supported languages
- BlackBerry Dynamics software versions
- Requirements
- Compatibility with earlier releases
- Software requirements
- BlackBerry Dynamics entitlement ID and version
- Supported launchModes
- Compatibility with the BlackBerry Dynamics Launcher Library
- Supported CPU architectures
- Supported and unsupported Android and third-party features
- FIPS-linking on Android: automatic
- Restricted key prefix
- Steps to get started with the BlackBerry Dynamics SDK
- Installing the BlackBerry Dynamics SDK for Android
- Integrating the BlackBerry Dynamics SDK in .aar format
- Using the branding API to add a custom logo and colors
- Info: Add Samsung Pass to your BlackBerry Dynamics app
- Info: APIs for secure clipboard management
- Info: Preventing autobackup to Google Drive
- Info: APIs for network status
- BlackBerry Dynamics SDK for Android: Wearable Framework
- Implementing SafetyNet attestation for BlackBerry Dynamics apps
- Programming with the BlackBerry Dynamics SDK and BlackBerry Enterprise Mobility Server services
- Sample apps
- Testing and troubleshooting
- Implementing automated testing for BlackBerry Dynamics apps
- Automated testing with the BlackBerry Dynamics sample apps
- Preparing for automated testing
- Components of a sample automated testing configuration
- Execute all tests from the command line with Gradle
- Execute specific tests from the command line with Gradle
- Execute tests from the Android Studio IDE
- Add automated testing to your BlackBerry Dynamics Android app
- Disable compliance settings that check for a compromised OS
- Emulators and the rooted OS compliance policy
- Using enterprise simulation mode
- Logging and diagnostics
- Implementing automated testing for BlackBerry Dynamics apps
- Readying your app for deployment: server setup
- Details of support for client certificates
- BlackBerry Docs
- BlackBerry Dynamics SDK for Android 5.0
- BlackBerry Dynamics SDK for Android Development Guide
- Steps to get started with the BlackBerry Dynamics SDK
- Installing the BlackBerry Dynamics SDK for Android
- High-level directory structure of the BlackBerry Dynamics SDK for Android
High-level directory structure of the BlackBerry Dynamics SDK for Android
BlackBerry Dynamics SDK for Android
The
BlackBerry Dynamics SDK for Android
includes the following artifacts:
- A Library project that contains the resources needed for the UI to run in eachBlackBerry Dynamics-enabled app
- A.jarfile that contains allBlackBerry DynamicsAPIs and implementations
- TheBlackBerry Dynamicsnative library containing the native code
Handhelds vs. Wearables subdirectory naming convention
The
BlackBerry Dynamics SDK for Android
has a major division between support for handheld devices and support for wearable devices with the BlackBerry
Dynamics
Wearable Framework. The pertinent directory structure looks like the following. Nested in these directories are the appropriate .so
and .jar
files you need to include in your project, along with other support files.
- Handheld libraries:sdk_installation_directory/sdk/libs/handheld/gd
- Wearable libraries:sdk_installation_directory/sdk/libs/wearable/gd_wearable_framework