- 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
 
 - 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
 
Using Kerberos
    Kerberos
BlackBerry
        Dynamics
 apps support both Kerberos
 PKINIT with PKI certificates and Kerberos
 Constrained Delegation. Kerberos PKINIT and Kerberos
 Constrained Delegation are distinct implementations of Kerberos
. You can support one or the other for BlackBerry
        Dynamics
 apps, but not both.With 
Kerberos
 PKINIT, authentication occurs directly between the BlackBerry
        Dynamics
 app and the Windows
 Key Distribution Center (KDC). User authentication is based on certificates that are issued by Microsoft Active
  Directory
 Certificate Services. No additional programming is required by the app developer to use Kerberos
 PKINIT.With 
Kerberos
 Constrained Delegation, authentication is based on a trust relationship between the management server (BlackBerry UEM
 and a KDC. The management server communicates with the service on behalf of the app.For more information about how to configure the desired 
Kerberos
 implementation in UEM
, including requirements and prerequisites, see Configuring Kerberos for BlackBerry Dynamics apps in the UEM Administration Guide
.