Dynamic App Content Delivery for Low-Latency Updates
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Managing native applications is inefficient due to large installation packages containing all presentable content, leading to memory waste and slow download speeds, and updates require substantial time and effort from developers and users.
Innovation Solution
Separate presentable content from programming logic, allowing applications to dynamically retrieve content from a content delivery network based on user attributes and needs, reducing package size and enabling faster updates.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If all presentable content is included in the installation package, then the application can run offline with complete content, but the package size becomes unnecessarily large causing inefficient memory use and slow download speed
Solution Approach 1:
The patent segments presentable content into multiple language versions and stores them separately on the server. The installation package includes only the base application code without bundled content, while content is delivered dynamically based on user needs, achieving offline capability for used content without storing all possible content locally
Solution Approach 2:
The patent extracts presentable content from the installation package and stores it separately on the content delivery network. This extraction allows the application to be installed with minimal size while still providing offline access to content that is dynamically downloaded and cached based on user attributes and usage patterns
2Speed
If the application package is reduced in size by excluding presentable content, then download speed and memory efficiency improve, but the application requires network connection to access content
Solution Approach 1:
The patent performs preliminary actions by pre-processing presentable content into different language versions and storing them on the content delivery network before user requests. When users access the application, their preferred language content is downloaded and cached in advance, enabling offline operation without requiring the full content set to be pre-installed
3Adaptability or versatility
If all language versions of presentable content are included in update packages, then language support is maintained, but the update package size becomes large causing inefficient bandwidth use and slow update speed
Solution Approach 1:
The patent applies local quality by delivering content in the specific language version needed by each user based on their device attributes. Update packages contain only the language variants required for that particular user, not all possible language versions, thereby reducing bandwidth consumption while maintaining multi-language support capability
4Loss of information
If presentable content is updated by releasing a new application version, then content updates are achieved, but the update process becomes burdensome requiring substantial time and effort from developers and users
Solution Approach 1:
The patent segments the application into independent components: the stable programming logic packaged as the application binary, and the updateable presentable content stored separately on the content delivery network. This allows content to be updated independently without requiring new application versions, reducing update time and developer effort while maintaining content timeliness
Data Source
Figure 1
Figure 2
Figure 3A
AI summary
Methods and systems are presented for providing low latency dynamic content updates to applications, by separating presentable content from the programming logic of an application. The programming code associated with the application without at least a portion of the presentable content may be released to an application hosting server for distributing to end-users. The presentable content may be published to a content delivery network separate from the application hosting server. Once the application is downloaded to a user device, the application may retrieve the presentable content from the content delivery network. The application may incorporate the retrieved presentable content into the application such that the presentable content would be presented on the user device as intended when the application is accessed.