Get Your App to Work at Work
summary
Android Enterprise splits work and personal data using work profiles and three components: managed Google Play, enterprise cloud APIs (EMM) and the Device Policy Controller. Apps must use the enterprise contacts content URI and check isEnterpriseDirectoryId/isRemoteDirectoryId while still requesting READ/WRITE_CONTACTS; share files with a FileProvider to generate content URIs instead of file paths; call resolveActivity before startActivity because intents don’t cross profiles by default; declare managed configurations in the manifest, read them via RestrictionsManager, send feedback with the Android Enterprise feedback library, and test with Test DPC.
AI-written summary · about
chapters (8)
- 0:00Introduction to work profiles
- 3:28What is Android Enterprise
- 5:13Work profile compatibility best practices
- 8:26Handling contacts and files across profiles
- 9:52Intent handling in work profiles
- 11:37Leveraging managed configurations
- 14:24Testing with Test DPC app
- 16:13Q&A and resources
related talks
37mThe World of Android Enterprise Every Business App Developer Should Know
16mWriting Apps for the Work Profile
30mTHE POWER OF EMM: DEPLOY ENTERPRISE-READY APPS FASTER
34mThe World of Device Management Enabled by Android Enterprise
37mAndroid Enterprise: the developer's missing manual
40mBEST PRACTICES FOR ANDROID ENTERPRISE APPLICATION DEVELOPMENT
28mKEYNOTE: WHAT'S NEXT FOR ANDROID IN THE ENTERPRISE
35mMANAGE ANDROID WITHOUT AN APP: THE ANDROID MANAGEMENT API