Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
For video collaboration devices, the user experience is locked to interface defined by service provider or Partner, running immediately after device bootup, with system gestures and actions disabled. Users can sign in and sign out using corporate credentials, see upcoming meetings, place/accept an outgoing call (audio/video), and manage meetings. Upon OOBE completion, the Teams app is considered the root-level UI.
Design includes:
- Custom Launcher,
- System UI customizations,
- Keyboard customizations
Restricting the user only to the selected experience (application) is accomplished as a by-product of the customizations that MDEP does to the Launcher and the System UI. Simply put, the user will have no way of leaving the dedicated app or navigating to other Android experiences. However, for extra security, MDEP can use the lock task mechanism to explicitly restrict the user to a specific set of apps. While these common principles will be used across multiple verticals, actual implementation of Custom Launcher and System UI is product specific.