Application Crash Management via Dynamic User Grouping
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Social networking systems face challenges in managing application crashes, particularly when a small percentage of users experience issues due to specific features, making it inefficient to allocate resources to address these problems.
Innovation Solution
A system that identifies users experiencing frequent crashes due to specific application features, ranks them into a high crash user group, disables the problematic feature for this group, and periodically rotates users in and out of the group to update the user experience.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If the application feature is disabled for all users to prevent crashes, then application reliability is improved, but device complexity and resource allocation efficiency deteriorate
Solution Approach 1:
The patent applies local quality by differentiating the treatment of users based on their crash experience. Instead of uniformly disabling the feature for all users, the system identifies a specific subgroup (high crash user group) and applies the feature disablement only to them. This localized approach maintains application reliability for affected users while preserving feature functionality for the majority of users who do not experience crashes, thereby optimizing resource allocation and reducing unnecessary complexity.
2Reliability
If the application feature is disabled for the high crash user group, then application crashes are reduced, but user engagement and ease of operation deteriorate
Solution Approach 1:
The patent implements dynamics by making the feature availability conditional and changeable based on user experience over time. Users are dynamically moved into the high crash user group when they experience crashes, resulting in feature disablement. However, if they stop experiencing crashes, they are eventually removed from the group and regain access to the feature. This dynamic adjustment balances crash reduction with user engagement, allowing users to benefit from the feature when it works properly while protecting them when it causes issues.
3Reliability
If users are continuously monitored and grouped based on crash data, then application reliability is improved, but measurement precision requirements and device complexity increase
Solution Approach 1:
The patent applies the taking out principle by extracting and isolating the crash-related data from the overall application data. The system specifically identifies and tracks crash events, separating them from other application operations. This extraction allows for precise measurement of crash frequency and patterns without requiring comprehensive analysis of all application activities, thereby reducing the overall measurement precision requirements while maintaining effective crash management through focused data collection on crash-specific metrics.
Data Source
AI summary
Systems, methods, and non-transitory computer-readable media can determine an application feature causing an application to crash. A set of users is ranked based on application data. The application data comprises crash cause data indicative of the number of times the application feature caused the application to crash for a user. A high crash user group is determined based on the ranking the set of users. The application feature is disabled for the high crash user group. A subset of the high crash user group is periodically replaced with a set of new users not currently in the high crash user group.


