Stand-alone Interpreter Engine for Inactive App Updates
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Updating applications on mobile devices with limited resources can lead to performance degradation due to the need for full-featured interpreter engines, which consume significant memory and processing power, especially when updating inactive applications.
Innovation Solution
Employing a stand-alone interpreter engine module with reduced functionality and a smaller memory footprint to process update information for inactive applications, avoiding the launch of full-featured engines and minimizing performance impact.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If a full-featured interpreter engine is used to update inactive applications, then the application can be updated with complete functionality, but memory usage and processing power consumption increase significantly
Solution Approach 1:
The interpreter engine is segmented into two distinct modes: a headless mode for background update operations and a graphical mode for user-facing operations. This segmentation allows the system to use only the necessary subset of engine functionality for each task, reducing resource consumption during application updates while maintaining complete update capability when needed.
Solution Approach 2:
For updating inactive applications, the system employs partial action by using only the headless mode of the interpreter engine, which provides the minimum necessary functionality to process update information without the overhead of graphical interface components. This partial execution achieves the update goal while minimizing resource usage.
2Adaptability or versatility
If a full-featured interpreter engine is launched to process update information, then all update operations can be performed, but device performance degrades due to high resource consumption
Solution Approach 1:
The system dynamically selects the appropriate interpreter engine mode based on the operational context. When updating inactive applications, it dynamically switches to headless mode for efficient resource utilization. When user interaction is required, it dynamically transitions to graphical mode. This dynamic adaptation maintains versatility while preserving device performance.
3Reliability
If the full-featured interpreter engine is used for background updates, then complete update functionality is available, but startup time and memory footprint increase
Solution Approach 1:
The graphical interface components are extracted from the headless mode interpreter engine, creating a streamlined version that contains only the essential update processing functionality. This extraction removes unnecessary overhead, reducing both startup time and memory footprint while preserving complete update capability for background operations.
Data Source
AI summary
Techniques are described for updating applications installed on devices. The applications may include native applications having a web view component to handle interpreted language instructions. The applications may also include web applications executable within a browser. A message may be sent to a computing device, the message including update information specifying one or more updates to the state or the features of an application. The update information may be described using interpreted language instructions. To handle the updates to an application in instances when the application is inactive, a stand-alone interpreter engine may be employed instead of the web view component or instead of the interpreter engine included in a browser. Use of the stand-alone interpreter engine may mitigate possible performance effects or intrusive user interface elements from launching the web view component or the browser-based interpreter engine to perform update operations.