In-Application Dynamic Content Loading With Local and Remote Routing
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Developers of applications are restricted by operating systems and application stores from providing dynamically updating content, leading to delayed user experiences and impaired functionality, particularly for mobile devices.
Innovation Solution
Implement a content handler that intercepts requests for application assets, redirecting them to local or remote sources based on availability, using a custom URL scheme to bypass operating system restrictions, allowing seamless dynamic content loading.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Speed
If applications are downloaded for local execution, then execution latency is reduced, but dynamic content updates require updates and further downloads which are constrained by publisher policies
Solution Approach 1:
The patent segments the application into two distinct parts: a core application package that is downloaded and installed locally, and dynamic content assets that are loaded separately from remote sources. This segmentation allows the core application to execute locally with low latency while dynamic content can be updated independently without requiring full application updates or adhering to publisher download constraints.
Solution Approach 2:
The patent introduces a content handler as an intermediary component that sits between the application and remote content sources. This content handler manages the loading, caching, and updating of dynamic content assets, enabling the application to access updated content without direct publisher store involvement and bypassing traditional update constraints.
2Adaptability or versatility
If applications are provided online, then dynamic updates are enabled, but execution latency increases and user experience is impaired
Solution Approach 1:
The application is divided into a locally-executable core component and remotely-loaded content assets. The core application package is downloaded once and executed locally, providing fast execution latency, while dynamic content is segmented into separate assets that can be updated without re-downloading the entire application.
Solution Approach 2:
The core application package is downloaded and installed in advance before execution is needed, enabling immediate local execution with minimal latency. Dynamic content assets are then loaded on-demand from remote sources, combining the benefits of pre-localization for speed with remote loading for dynamic updates.
3Reliability
If application stores restrict content types in updates, then security and quality control are maintained, but developers are restricted from offering applications with dynamically updating content
Solution Approach 1:
A content handler acts as an intermediary layer between the application and remote content sources, managing content loading and updates. This intermediary enables developers to provide diverse dynamic content types without direct publisher store intervention, while the content handler itself can implement appropriate security and quality controls for the dynamic content it manages.
Solution Approach 2:
The application structure separates the publisher-controlled core package from developer-controlled dynamic content assets. This segmentation allows developers to update dynamic content with greater flexibility and variety, while the core application remains under publisher control for security and quality assurance.
Data Source
AI summary
In some aspects, the disclosure is directed to methods and systems for in-application dynamic content loading via a hybrid process, including both local and remote content items, via a content handler intercepting requests in a predetermined uniform resource locator (URL) scheme and redirecting the requests to local storage or a remote content provider, transparently to a browser application or webview of the application, and avoiding restrictions imposed by an operating system of the device. Content may be dynamically updated on the content provider server by developers, and dynamically loaded during execution of the application on client devices, without requiring updates to be provided to an application store or publisher server.