Interface Template Engine for Dynamic UI Updates

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing client applications require recompilation, re-downloading, and re-installation when the interface framework needs to be changed or updated, preventing users from accessing new or changed service data without updating the client application.

Innovation Solution

Implementing an interface data presenting method and device that uses interface template technology instead of native code, allowing dynamic updates to the client application's interface by parsing and rendering structured data from a server, eliminating the need for proprietary protocol knowledge and enabling universal solutions.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If the interface framework is changed or updated based on service data changes, then the interface can adapt to new service requirements, but the client application needs to be recompiled, re-downloaded, and re-installed

Engineering Contradiction:
Improveinterface adaptabilityVSAvoidupdate time
Core Design Contradiction:
Adaptability or versatilityVSLoss of time

Solution Approach 1:

The interface framework is segmented into independent interface templates that can be updated separately from the client application. The template engine allows parsing and rendering of interface templates without requiring client recompilation, enabling incremental updates to the interface layer only.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

A template engine acts as an intermediary between the interface framework and the client application. This intermediary component enables dynamic rendering of interface templates using service data, allowing updates to be applied without direct modification of the client application's native code.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Adaptability or versatility

If proprietary protocol markup language is used for interface templates, then the interface can be customized for specific services, but developers need to learn and master complex proprietary protocols

Engineering Contradiction:
Improveinterface customizationVSAvoiddeveloper ease
Core Design Contradiction:
Adaptability or versatilityVSEase of manufacture

Solution Approach 1:

The system adopts universal markup languages (such as HTML, XML, or JSON) instead of proprietary protocols for interface template definition. This allows developers to use familiar, standard languages while the template engine provides the necessary functionality for service-specific customization, eliminating the need to learn complex proprietary protocols.

Inventive Principle:
Principle #6Universality (Multi-functionality)

3Adaptability or versatility

If the client application is updated to reflect interface changes, then new service data can be presented to users, but users experience service disruption during update

Engineering Contradiction:
Improveservice data presentationVSAvoidservice continuity
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The interface framework transitions from a static, compiled structure to a dynamic, renderable template system. Interface templates can be updated and rendered in real-time without requiring client application updates, allowing the system to adapt to changing service data while maintaining continuous service availability.

Inventive Principle:
Principle #15Dynamics

Data Source

PatentUS11216610B2Generating a graphical user interface based on formatted structure data
Publication Date: 2022.01.04 ADVANCED NEW TECHNOLOGIES CO LTD
  • US11216610B2 patent drawing
  • US11216610B2 patent drawing
  • US11216610B2 patent drawing

AI summary

Methods, systems, and computer-readable storage media for generation of a unified view of the graphical user interface. Implementations include actions of receiving, from a server, structured data of an interface template that is generated by the server by parsing interface template data associated with the interface template. The interface template is identified based on an interface identifier included in the service data. A virtual view node for the widget is determined based on the structured data. The widget is retrieved based on the location information associated with the virtual view node. A unified view of the graphical user interface is generated by rendering the widget with a plurality of widgets associated with the graphical user interface and is displayed on a display device.