Application Update Distribution Control via Uninstall History
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Game developers face the challenge of creating multiple versions of a native gameplay experience for various devices, and users must manually switch and load games across devices, leading to inefficiencies in application updates and management.
Innovation Solution
A system and method that monitor the uninstall and reinstall history of applications across devices to determine the frequency of updates, discontinuing updates if the frequency exceeds a threshold, ensuring that updates are only distributed when necessary, thereby optimizing resource allocation and user experience.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If application updates are distributed to all users regardless of usage patterns, then developers ensure all users have access to latest features and bug fixes, but users who frequently uninstall and reinstall applications receive unnecessary updates wasting bandwidth and storage resources
Solution Approach 1:
The system monitors uninstall and reinstall events across the user base and uses this feedback data to dynamically adjust update distribution decisions. When a threshold of frequent uninstalls is detected, the system responds by stopping further update distributions for that application, thereby avoiding waste of resources on users who do not retain the application.
Solution Approach 2:
The system changes the parameter of update distribution status from 'continuous' to 'discontinued' based on monitored usage patterns. By tracking the frequency of uninstall/reinstall cycles and comparing against predefined thresholds, the system dynamically adjusts the update distribution parameter to optimize resource utilization while maintaining reliability for retained users.
2Adaptability or versatility
If developers create multiple versions of applications for different devices, then each device receives optimized performance, but the complexity of application management and update distribution increases significantly
Solution Approach 1:
The system implements a universal update distribution mechanism that works across multiple device types and operating systems. Rather than maintaining separate complex update systems for each device version, a single unified system monitors uninstall patterns across all platforms and applies update distribution decisions universally, simplifying management while preserving device-specific optimization capabilities.
3Adaptability or versatility
If users manually switch between devices to access their preferred game version, then users can choose their optimal gaming experience, but user convenience and time efficiency decrease
Solution Approach 1:
The system automatically monitors and analyzes user application retention patterns across devices without requiring manual user input or intervention. By self-service monitoring of uninstall/reinstall events and automatically making update distribution decisions, the system eliminates the need for users to manually manage device switching while still providing optimized gaming experiences based on actual usage data.
Data Source
AI summary
A communication device may determine whether an installed application should be updated based on an uninstall and/or reinstall history of the application and control distribution of updates to the installed application based on the determination. A frequency at which the application is uninstalled and/or reinstalled on the communication device or other device utilized by the user of the communication device may be determined based on the monitored usage of the application. The distribution of the updates to the application may be discontinued when the frequency exceeds a particular threshold. The distribution of the updates may continue when the frequency is below the particular threshold. A version number of the installed application may be compared to a corresponding version number of a version of the application that is stored on a remote server in order to determine when the update to the application is available for distribution.