Launcher Connectivity Detection for Shared Mobile Devices
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In enterprise environments, management systems face challenges when client devices, such as smartphones and laptops, experience connectivity issues due to failed authentication flows, rendering them unusable even if they have network access, as they rely on network infrastructure, directory services, and identity providers.
Innovation Solution
A launcher application with connectivity detection capabilities is implemented, allowing mobile devices to detect connectivity modes and adapt by using a configurable set of endpoints, ensuring that essential applications can still be launched even if some connectivity components are unavailable, by utilizing resource identifiers for health checks and determining launchable subsets of applications based on connectivity status.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If the launcher application requires constant network connectivity to management services, directory services, and identity providers, then security policies can be enforced and applications can be launched in the network environment, but the client device becomes unusable when connectivity fails
Solution Approach 1:
The launcher application dynamically adapts its behavior based on connectivity status. It monitors network availability and transitions between different operational modes (full network access mode, limited functionality mode, offline mode), adjusting which applications can be launched and what features are available based on current connectivity conditions to management services, directory services, and identity providers.
Solution Approach 2:
The application catalog is segmented into different groups based on connectivity requirements. Applications are categorized as requiring full network connectivity, partial connectivity, or no connectivity. This segmentation allows the launcher to selectively launch appropriate applications based on current network conditions, ensuring critical functions remain available even when connectivity to management services fails.
2Reliability
If the launcher application restricts application launch to maintain security when connectivity is limited, then security is preserved, but user productivity decreases
Solution Approach 1:
Different security policies are applied locally based on connectivity context. When full connectivity is available, standard enterprise security policies are enforced. When connectivity is limited or lost, the system applies alternative security measures locally on the device, such as using cached authentication tokens, local device policies, or sandboxed execution environments, allowing productivity to continue while maintaining appropriate security controls for the current context.
Solution Approach 2:
The system prepares for potential connectivity loss by pre-caching authentication credentials, security policies, and critical application data before network disruptions occur. It establishes offline operational modes in advance with pre-configured security parameters, allowing the device to maintain secure operation during connectivity outages without requiring real-time validation with management services.
3Productivity
If the launcher application allows applications to launch without verifying network connectivity, then user productivity is maintained, but security risks increase
Solution Approach 1:
The launcher application implements continuous feedback mechanisms to monitor connectivity status, authentication state, and security policy compliance. It actively checks whether the device can communicate with management services, directory services, and identity providers before and during application execution. Based on this feedback, it dynamically adjusts which applications can launch and enforces appropriate security controls, ensuring that productivity is maintained only when security conditions are satisfied.
Solution Approach 2:
An intermediary security layer is introduced between the application catalog and the launch process. This intermediary verifies connectivity requirements, validates authentication status, and enforces security policies before allowing applications to execute. It acts as a gatekeeper that can permit productive operations when safe and block potentially risky operations when connectivity verification fails, balancing productivity and security needs.
Data Source
AI summary
Disclosed are approaches for a launcher application with connectivity detection for shared mobile devices. In some examples, among others, a management service component, a client device component, an enterprise environment component, or other connectivity endpoints associated with a plurality of applications can be identified. At least one response to requests transmitted to the connectivity endpoints can be received. A mode of connectivity can be determined based on the response. An application which is launchable in the mode of connectivity can be launched in an instance in which a selectable representation for the application is selected in a user interface.