Stub Application Preinstallation for Mobile Devices
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Mobile communication devices face challenges in efficiently preinstalling applications without increasing overhead costs, such as battery drain and memory usage, while also ensuring user convenience and exposure to new applications.
Innovation Solution
The implementation of stub applications with limited functionality, represented as interactive thumbnail images, which can be updated to full applications upon user request, reducing the need for direct preinstallation and minimizing resource usage.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If full applications are preinstalled on mobile communication devices, then user convenience and exposure to applications is improved, but overhead costs such as battery drain and memory usage increase
Solution Approach 1:
The application is segmented into two parts: a lightweight stub application that performs basic functions and a full application that provides complete functionality. The stub application is preinstalled on the device, while the full application is downloaded on-demand to a remote server or local storage, resolving the contradiction between providing user convenience through preinstallation and reducing battery drain by minimizing local application footprint.
Solution Approach 2:
A stub application serves as an intermediary between the user and the full application. The stub provides initial access points and basic functionality, while delegating heavier operations to the full application when needed. This intermediary approach allows users to benefit from having applications preinstalled without the full resource overhead, as the stub is minimal in size and resource consumption.
2Ease of operation
If full applications are preinstalled on mobile communication devices, then user convenience and exposure to applications is improved, but memory usage increases
Solution Approach 1:
The application is segmented into two parts: a lightweight stub application that performs basic functions and a full application that provides complete functionality. The stub application is preinstalled on the device, while the full application is downloaded on-demand to a remote server or local storage, resolving the contradiction between providing user convenience through preinstallation and reducing battery drain by minimizing local application footprint.
Solution Approach 2:
Instead of installing the complete application locally, a simplified copy (stub application) is preinstalled that provides essential functionality and access points. The full application can be accessed remotely or downloaded when needed, significantly reducing local memory usage while maintaining user convenience for basic operations.
3Use of energy by moving object
If stub applications are used instead of full applications, then overhead costs are reduced, but application functionality is limited
Solution Approach 1:
The system dynamically adapts between stub and full application modes based on user needs. The stub application provides basic functionality with minimal resource usage, while the system can dynamically load or access the full application when enhanced functionality is required, allowing the application to be both energy-efficient and versatile depending on operational context.
Solution Approach 2:
The stub application serves multiple functions: it provides basic application functionality, acts as a launcher for the full application, manages updates, and coordinates with remote servers. This multi-functionality allows the stub to compensate for its reduced size by being a versatile component that handles various operational requirements.
Data Source
AI summary
A mobile communication device comprises a processor, a memory, a plurality of stub applications comprising updateable version numbers, and a widget stored in the memory that, when executed by the processor, configures the processor to: determine a plurality of the stub applications to present, present the stub applications on a display of the mobile communication device, and elicit, in response to selection of a first stub application, retrieval and installation of a first full application in place of the first stub application.


