Linked-App Page Display via Preset Plug-In at App Exit
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing application distribution methods require users to download and manage multiple application stores and manually uninstall unused applications, leading to complexity and inefficiency.
Innovation Solution
A decentralized page display method and apparatus that integrates a preset plug-in to manage linked applications, allowing seamless startup and display of linked application pages upon exit or before startup of a target application, reducing installation size and maintaining user experience.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If users download and install multiple application stores to access different applications, then application selection diversity is improved, but device complexity and operation complexity increase
Solution Approach 1:
The patent merges multiple application store functions into a single integrated application store interface. Different application sources (system applications, third-party applications, operator applications) are unified under one store, allowing users to access diverse applications without installing multiple separate application stores. This consolidation maintains application selection diversity while reducing system complexity.
Solution Approach 2:
The application store is designed with universal functionality to handle multiple types of applications (system apps, third-party apps, operator apps) through a single interface. The store can display, download, and manage various application types without requiring separate application store installations, thereby improving adaptability while controlling device complexity.
2Productivity
If users manually download and uninstall applications through centralized stores, then application distribution control is improved, but ease of operation deteriorates
Solution Approach 1:
The patent implements a self-service mechanism where the application store automatically manages application downloads, installations, and uninstallations. When users select an application to uninstall, the system automatically handles the removal process and related cleanup tasks without requiring manual intervention for each step. This automation maintains distribution control while significantly improving ease of operation.
Solution Approach 2:
The application store acts as an intermediary between users and the application distribution system. It provides a unified interface that simplifies complex distribution operations into simple user actions (select, download, install, uninstall). The store manages the backend complexity of application deployment and removal, shielding users from operational complexity while maintaining efficient distribution control.
3Productivity
If application store is downloaded separately before accessing applications, then application distribution control is improved, but loss of time increases
Solution Approach 1:
The system performs preliminary actions by pre-loading and caching application metadata, descriptions, and installation information in the application store before users actually need to download or install applications. This preliminary preparation allows the store to quickly present application options and initiate downloads without requiring users to wait for initial store setup or metadata retrieval, thereby reducing perceived download time while maintaining distribution control.
Solution Approach 2:
The application store maintains continuous availability and readiness by keeping the service running and pre-fetching information in the background. Instead of requiring a separate initial download phase, the store continuously provides application information and manages downloads as users interact with it, eliminating idle time and maintaining productive action throughout the user experience.
Data Source
AI summary
A page display method includes: determining, in response to a startup of a target client, whether the target client is started for a first time; in response to determining that the target client is started for the first time, starting a target application in the target client; obtaining linked application data and display configuration information by a preset plug-in, where the linked application data includes a plurality of linked applications corresponding to the target application; determining, based on the display configuration information, whether to display a linked application page after an application exits; and in response to determining that the linked application page is to be displayed, ending the target application in the target client and displaying, by the preset plug-in and in the target client, the linked application page according to the linked application data in response to receiving an exit trigger for the target application.