- What is the BlackBerry Dynamics SDK?
- Requirements and support for platform-specific features
- Steps to get started with the BlackBerry Dynamics SDK
- Integrating optional features
- Enforcing local compliance actions
- Adding custom policies for your app to the UEM management console
- Add a watermark to the screens in a BlackBerry Dynamics app
- Using the BBWebView library
- Using the OkHttp HTTP framework
- Prompt the user to update a BlackBerry Dynamics app
- Adding a custom logo and colors with the branding API
- Support for Night Mode
- Using zero sign-on for SaaS services through BlackBerry Enterprise Identity
- Integrating BlackBerry Enterprise Mobility Server services
- Implementing the BlackBerry Dynamics Launcher
- Integrating BlackBerry Analytics
- Implementing Play Integrity attestation for BlackBerry Dynamics apps
- 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
- Configure compliance settings so you can debug your app
- Emulators and the rooted OS compliance setting
- Using enterprise simulation mode
- Troubleshooting common issues
- Logging and diagnostics
- Implementing automated testing for BlackBerry Dynamics apps
- Deploying your BlackBerry Dynamics app
- Deploying certificates to BlackBerry Dynamics apps
- BlackBerry Docs
- BlackBerry Dynamics SDK for Android 13.0
- BlackBerry Dynamics SDK for Android Development Guide
- Deploying your BlackBerry Dynamics app
- Using an obfuscation tool in your build and release process
Using an obfuscation tool in your build and release process
After your app is fully tested and ready to deploy, it is recommended that you use an obfuscation tool as part of your formal build and release process. It is a best practice to use
ProGuard
because it is the default obfuscation tool for Android
.For more information about the code obfuscation configuration and sample code that you can use, see the Build-Time Configuration appendix in the
BlackBerry Dynamics SDK for Android
API Reference.The
BlackBerry Dynamics SDK
uses Platform APIs, some of which rely on an API level later than the current minimum supported API level. A target SDK below the latest API level might throw warnings. The BlackBerry Dynamics SDK
ensures that the appropriate runtime checks are made before it attempts to use an API. You can ignore warnings about APIs that aren't found in BlackBerry
Dynamics
SDK classes with -dontwarn com.good.gd
.