Server-Based UI Rendering for Flexible Component Updates
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing user interface (UI) rendering technologies face challenges in flexibility and scalability, particularly in updating UI layouts and functionalities without over-the-air (OTA) updates and managing individual UI components effectively.
Innovation Solution
A server-based UI rendering approach where a computer system determines UI components, their associations, and availability information to generate rendering instructions that include presentation properties and event information, allowing for flexible and scalable UI management without the need for OTA updates.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If traditional UI rendering approaches are used, then UI components can be displayed, but flexibility and scalability for updates without OTA updates are limited
Solution Approach 1:
The patent extracts the UI rendering logic from the client device and relocates it to a remote server. The server generates rendering instructions based on UI component definitions and event information, then transmits these instructions to the client device for execution. This extraction enables flexible UI updates without requiring OTA updates to the client device, as the rendering logic can be modified on the server side.
Solution Approach 2:
The patent introduces rendering instructions as an intermediary layer between the UI component definitions and the client device display. These instructions act as a mediator that translates UI component definitions into device-specific rendering commands, enabling flexible UI management and updates without direct modification of the client device software.
2Productivity
If comprehensive UI component management is implemented, then UI functionality is enhanced, but processing and presentation latency increases
Solution Approach 1:
The patent implements caching policies where the server pre-generates and stores rendering instructions for UI components based on their definitions and event information. When the client device requests UI rendering, the server can retrieve pre-computed instructions from the cache rather than generating them in real-time, significantly reducing processing latency while maintaining comprehensive UI component management.
Data Source
AI summary
Techniques for server-based UI rendering are described. In an example, a system receives, from a device, a request associated with rendering a UI that includes multiple UI components. The system receives, from a first source associated with a first UI component, availability information indicating that the first UI component is available for use by other UI components. Based at least in part on the availability information, the system determines that the first UI component is available for use by a second UI component. The system receives, from a second source associated with the second UI component, event information indicating content presentable in the first UI component and an event trigger at the second UI component to present the content. Further, the system sends, to the device, a set of instructions associated with the rendering of the UI. The set of instructions includes the event information.