Dual UI Engine Architecture for Cross-Platform Interface Adaptation

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Developers face challenges in creating user interfaces (UIs) that adapt to different operating systems and provide rich functionalities, as existing methods are platform-specific and require complex implementation.

Innovation Solution

A method and apparatus that utilize two different interface description languages, one general-purpose and one customized, to generate UIs that can adapt to multiple operating systems, allowing for enhanced UI programming capabilities and rich view effects.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If developers use a platform-specific interface description language to develop UI, then the UI can be implemented on that specific platform, but the UI cannot adapt to other operating systems and requires separate development for each platform

Engineering Contradiction:
ImproveUI adaptability across operating systemsVSAvoidDevelopment complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The interface description is segmented into two distinct parts: a first description file using a first interface description language and a second description file using a second interface description language. Each file targets a specific platform, allowing the UI to be adapted to multiple operating systems while maintaining organized, manageable code structures for each platform

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The system implements multi-functionality by enabling a single UI design to be described in multiple interface description languages and executed on different operating systems. The first and second UI engines respectively parse and execute their corresponding description files, making the UI development process universal across platforms rather than platform-specific

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

2Adaptability or versatility

If developers create rich functionality UIs using customized interface description languages, then the UI provides enhanced programming capabilities, but the implementation becomes more complex

Engineering Contradiction:
ImproveUI programming capabilityVSAvoidDevelopment ease
Core Design Contradiction:
Adaptability or versatilityVSEase of manufacture

Solution Approach 1:

The system applies local quality by allowing different interface description languages to be used in different description files within the same application. Developers can select the most appropriate language for each specific UI component or platform requirement, optimizing programming capability locally while maintaining overall system coherence

Inventive Principle:
Principle #3Local quality

Solution Approach 2:

The first and second UI engines act as intermediaries between the interface description files and the rendering system. These engines translate and execute their respective description files, bridging the gap between different interface description languages and the final UI implementation, thereby simplifying the development process despite using multiple languages

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentEP4722897A2User interface implementation method and apparatus
Publication Date: 2026.04.08 HUAWEI TECH CO LTD
  • EP4722897A2 patent drawingFigure 1
  • EP4722897A2 patent drawingFigure 2
  • EP4722897A2 patent drawingFigure 3

AI summary

Embodiments of this application provide a user interface implementation method and an apparatus, and relate to the field of terminal technologies. An application installation package of a first application includes a first description file and a second description file that are used to perform interface description and interface behavior definition on a UI of the first application. The first description file and the second description file use different interface description languages. The first description file uses a first interface description language, and the second description file uses a second interface description language. When an electronic device runs the first application, a first UI engine reads, parses, and executes the first description file, to generate a first part of a first UI; and a second UI engine reads, parses, and executes the second description file, to generate a second part of the first UI. The first UI engine may be a general-purpose operating system engine. The second UI engine is not related to an operating system platform, can adapt to a plurality of operating system platforms, and has low technical implementation difficulty.