User-Specific Application Management on Shared Devices
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current Mobile Device Management (MDM) and Enterprise Mobility Management (EMM) systems face inefficiencies and security concerns when sharing devices among users, requiring multiple application instances and frequent re-provisioning, leading to excessive data consumption and user frustration.
Innovation Solution
Implementing user-specific applications on a shared device by using unique Package IDs to identify each user, allowing the device to display and hide applications accordingly, and retaining data for seamless user transitions without re-provisioning, while enabling shared applications to be used across multiple users.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If separate user spaces are used for all applications assigned to each user, then security is improved, but device complexity and resource footprint increase due to storing multiple versions of the same applications
Solution Approach 1:
The patent segments applications into two distinct categories: shared applications (accessible by multiple users) and user-specific applications (requiring separate instances). This segmentation allows the system to maintain security for sensitive applications while sharing common applications across users, thereby reducing the overall resource footprint while preserving security requirements.
Solution Approach 2:
The patent makes certain applications universal by allowing a single instance of shared applications to serve multiple users simultaneously. Applications marked as shareable can be accessed by any user on the device without requiring separate installations, thus reducing device complexity and resource consumption while maintaining functionality for all users.
2Reliability
If applications are wiped and re-provisioned each time a user logs out, then security is improved, but loss of time and productivity decrease due to excessive data consumption and reconfiguration requirements
Solution Approach 1:
The patent performs preliminary actions by pre-configuring applications with user-specific data and settings before the user needs them. User-specific applications are pre-provisioned with individual user credentials and preferences, so when users log in, their applications are already configured and ready to use, eliminating the need for re-provisioning and maintaining both security and productivity.
Solution Approach 2:
The patent introduces dynamic behavior to application provisioning by maintaining persistent user-specific application instances that automatically adapt to user login events. Instead of static wiping and re-provisioning, the system dynamically manages application visibility and access based on user authentication state, allowing seamless transitions while preserving user data and settings.
3Adaptability or versatility
If multiple concurrent copies of the same application are installed, then user-specific customization is improved, but device complexity increases due to operating system restrictions
Solution Approach 1:
The patent segments applications into shared and user-specific categories, allowing the operating system to manage installations efficiently. User-specific applications that require customization get separate instances, while shared applications use a single instance accessible by multiple users, thus achieving user-specific customization without excessive installation complexity.
Solution Approach 2:
The patent applies local quality by allowing different installation behaviors for different applications based on their classification. Some applications (user-specific) are installed with full customization capabilities for individual users, while other applications (shared) are installed once and shared across users, optimizing resource usage while maintaining necessary customization where required.
Data Source
AI summary
Examples described herein include systems and methods for providing user-specific applications on a shared user device. The user device can receive a first instance of an application having a Package ID that includes an identification of a first user. When the first user is logged in, the user device can display an icon associated with the first instance of the application, based on the Package ID including an identification of the first user. When the first user is not logged in, the user device can hide the first instance of the application. When a second user is logged in, the device can display a second instance of the application based on the Package ID of the second instance including an identification of the second user. The user device can also display the same instance of a shared application to both the first and second user.