Permission Request Segmentation for Mobile App Installation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Users are overwhelmed and frustrated by numerous permission requests when installing applications that access multiple computing resources, leading to potential security risks as they may hastily approve access without scrutinizing each request.
Innovation Solution
A method to categorize applications based on common permissions, where uncommon resource access requests are flagged and visually distinguished from common ones, allowing users to focus on atypical permissions that may pose higher security risks.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If the application requests access to numerous computing resources, then the application functionality is comprehensive, but the user experiences frustration and confusion due to the many permission requests
Solution Approach 1:
The patent segments the permission requests into two distinct categories: common permission requests (displayed in a first manner) and uncommon permission requests (displayed in a second manner). This segmentation allows users to quickly identify and focus on atypical permission requests that may pose security risks, while common requests are processed more efficiently. The segmentation resolves the contradiction by maintaining comprehensive application functionality while improving ease of operation through differentiated presentation.
Solution Approach 2:
The patent applies local quality by differentiating the visual presentation of permission requests based on their category. Common permission requests are displayed with one visual style (e.g., standard format), while uncommon permission requests are displayed with a distinct visual style (e.g., highlighted or emphasized format). This local differentiation helps users quickly identify potentially risky permissions without being overwhelmed by the total number of requests, thus improving user experience while maintaining comprehensive functionality.
2Productivity
If the user hastily approves all permission requests to speed up installation, then the installation process is faster, but security risks increase
Solution Approach 1:
The patent employs visual differentiation (analogous to color changes) by displaying uncommon permission requests in a distinct visual manner compared to common requests. This visual emphasis draws users' attention to potentially risky permissions, encouraging them to review these specific requests more carefully rather than hastily approving all requests. The visual distinction maintains installation speed while improving security awareness.
Solution Approach 2:
The patent performs preliminary classification of permission requests before presentation to the user. By pre-identifying which requests are common and which are uncommon based on the application category and historical data, the system prepares the permission display in advance. This preliminary action allows the system to present information in a security-conscious manner without delaying the installation process, thus maintaining productivity while improving reliability.
3Device complexity
If the system displays all permission requests in the same manner, then the interface is simple, but users cannot distinguish between common and atypical permission requests
Solution Approach 1:
The patent segments permission requests into common and uncommon categories with distinct visual presentations. This segmentation preserves interface simplicity by using clear, differentiated displays rather than complex explanations, while simultaneously preventing loss of information by making the distinction between common and atypical requests visually apparent. Users can quickly grasp the nature of each request without overwhelming complexity.
Solution Approach 2:
The patent uses visual differentiation (similar to color changes) to distinguish between common and uncommon permission requests. This approach maintains interface simplicity by using intuitive visual cues rather than complex text explanations, while effectively communicating the distinction between different types of permission requests. The visual distinction prevents information loss by making the categorization immediately apparent to users.
Data Source
AI summary
Methods and devices for managing permission requests to allow access to a computing resource are disclosed herein. In one example embodiment, the method comprises: for an application to be installed on the computing device, determining an application category that the application is associated with, and retrieving a common permissions list for the application category, wherein the common permissions list identifies at least one computing resource that applications associated with the application category are configured to access; during an installation of the application on the computing device, determining one or more computing resources on the computing device that the application is configured to access when the application is executed on the computing device; determining which computing resources, of the one or more computing resources on the computing device that the application is configured to access when the application is executed on the computing device, are not identified in the common permissions list; and for each computing resource that the application is configured to access when the application is executed on the computing device that is not identified in the common permissions list, providing, in a user interface of the computing device, a permission request to allow the application to access the computing resource.