UI Template Caching for Rapid Application Layout Updates
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing service-based application approaches for organizations to update or change the layout of an application's user interface (UI) are cumbersome and resource-intensive, requiring new application rollouts and deployments.
Innovation Solution
A templatization service that enables client-side template customization, allowing tenants to select and customize templates for application interfaces, which are cached on the client-side for efficient rendering and control, reducing the need for new application deployments.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If new application rollouts and deployments are performed to update UI layout, then the application interface can be updated, but computational resources and network resources are consumed excessively
Solution Approach 1:
The patent segments the application interface into separate template components that can be independently selected and customized. Instead of deploying a complete new application version, only the specific template portion needing update is modified and applied, reducing computational overhead while maintaining full UI adaptability
Solution Approach 2:
The patent creates and uses template copies that define interface layouts. These templates are cached on client devices, allowing updates to be applied by swapping template references rather than redistributing entire application packages, significantly reducing network and computational resource consumption
2Adaptability or versatility
If new application rollouts and deployments are performed to update UI layout, then the application interface can be updated, but time is consumed for deployment processes
Solution Approach 1:
The patent performs preliminary actions by pre-defining multiple UI templates and caching them on client devices during initial application setup. When updates are needed, pre-configured templates can be immediately activated without deployment delays, enabling rapid UI adaptation
Solution Approach 2:
Templates are copied to client-side cache during initial installation. Subsequent UI updates are applied by referencing updated template versions already present in the cache, eliminating the time-consuming process of redistributing entire application packages for each UI change
3Speed
If templates are cached on client device, then template retrieval speed improves, but client device storage is consumed
Solution Approach 1:
The patent applies local quality by caching templates selectively on client devices based on specific tenant selections and usage patterns. Only the templates actually needed by each tenant are stored locally, optimizing retrieval speed while minimizing storage consumption through targeted local caching rather than universal caching
4Adaptability or versatility
If application content is mapped to template sections, then content rendering flexibility improves, but processing complexity increases
Solution Approach 1:
The patent implements universal template sections that can accommodate multiple types of application content through standardized mapping rules. This multi-functional approach allows the same template structure to render different content types, increasing flexibility while reducing processing complexity through reuse of established mapping patterns
Data Source
AI summary
A system and method for application templatization that receives, via a template adapter, selection of a template for customization of content display for an application. Selections of template configuration options are received for the selected template. The selected template and template configuration options are stored with a template identifier for the application. A network call is received to fetch content for the application upon launch of an instance of the application at a user device. The network call includes the template identifier. In response to receiving the network call, content for the application is fetched and the template is retrieved using the template identifier. The fetched content is mapped to sections of the stored template using the stored template configuration options and the mapped application content is rendered for display on a user interface device.


