Open User Interface Framework for Custom Mobile App Controls

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current methods for designing, deploying, and managing mobile applications lack the ability to provide custom user interfaces and efficient customization options, limiting developers' flexibility and user experience.

Innovation Solution

A tool and framework that allows application designers to create and manage custom controls and user interfaces, enabling the use of custom classes and Open UI Field Adapter interfaces to define views programmatically, and allowing for branding and resource personalization, even before connecting to a server.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of manufacture

If standard controls and user interfaces are used in mobile applications, then development efficiency and consistency are improved, but customization capability and user experience differentiation are limited

Engineering Contradiction:
Improvedevelopment efficiencyVSAvoidcustomization capability
Core Design Contradiction:
Ease of manufactureVSAdaptability or versatility

Solution Approach 1:

The user interface is segmented into standard controls and custom controls. Standard controls provide consistent functionality across applications, while custom controls enable differentiated user experiences. The system allows developers to selectively use standard or custom controls based on application requirements, resolving the contradiction between consistency and customization.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The user interface framework dynamically loads and executes custom controls based on application definitions. Instead of a static set of predefined controls, the system can adaptively incorporate custom controls at runtime, enabling both efficient development using standard controls and flexible customization when needed.

Inventive Principle:
Principle #15Dynamics

2Adaptability or versatility

If custom user interfaces are implemented, then user experience and branding are improved, but development complexity and implementation difficulty increase

Engineering Contradiction:
Improvecustomization capabilityVSAvoiddevelopment complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The system introduces an intermediary framework that sits between the developer's custom controls and the execution environment. This framework handles the complexity of control registration, validation, and execution, allowing developers to focus on creating custom controls without managing the underlying implementation details.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

Custom controls are validated and registered before execution. The framework performs preliminary actions to ensure custom controls meet required standards and are properly integrated, reducing complexity during the execution phase and ensuring smooth operation of customized interfaces.

Inventive Principle:
Principle #10Preliminary action

3Reliability

If custom controls are validated against standards, then compliance and quality are improved, but validation time and processing overhead increase

Engineering Contradiction:
ImprovecomplianceVSAvoidvalidation time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

Custom controls undergo validation before execution, allowing the system to ensure compliance with standards in advance. This preliminary validation prevents runtime errors and ensures quality while enabling faster execution by pre-resolving validation requirements.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The validation process is optimized to skip unnecessary validation steps for controls that are certain to comply with standards, focusing validation resources only on controls that require verification. This reduces overall validation time while maintaining comprehensive compliance checking where needed.

Inventive Principle:
Principle #21Skipping (Rushing through)

Data Source

PatentUS9509761B2Open user interface
Publication Date: 2016.11.29 MATHESON TRI GAS INC
  • US9509761B2 patent drawing
  • US9509761B2 patent drawing
  • US9509761B2 patent drawing

AI summary

In an example embodiment, a definition is loaded into a client application for execution on a user device. Then, one or more classes defined in a central repository database of a server are loaded into the client application. It may then be determined that one or more custom classes not defined in the central repository database are contained in the definition. The one or more custom classes may be validated by ensuring that they contain one or more preset functions. The one or more custom classes may then be loaded into the client application, thereby overriding or extending at least one of the one or more classes defined in the central repository database.