Customizable UI Sections via Metadata for Cross-Platform Apps
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current computer systems face challenges in efficiently providing customized versions of applications across multiple platforms, as existing solutions limit flexibility and require significant modifications to both mobile applications and backend systems, often necessitating re-implementation by software vendors.
Innovation Solution
A client-based application architecture that allows for customizable user interface displays through section metadata, enabling a single version of the mobile application to accommodate customizations by a backend system, with section definition and customization systems that define and modify user interface sections, and a section accessing system that generates and renders user interface displays based on metadata.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If mobile applications allow users to use built-in functionality or change through settings, then the system flexibility is limited, but the device complexity is reduced
Solution Approach 1:
The patent introduces a metadata file as an intermediary between the mobile application and the backend system. This metadata file acts as a mediator that defines user interface sections and their corresponding backend fields, allowing customization without modifying the actual application code. The metadata serves as a configuration layer that bridges the fixed application structure with the need for organizational customization.
Solution Approach 2:
The user interface is segmented into discrete sections, each defined by metadata. This segmentation allows individual sections to be customized independently without affecting the rest of the application. Each section can be configured with specific fields, data types, and display properties through metadata, enabling granular customization while maintaining the overall application structure.
2Adaptability or versatility
If source code access is provided to allow organizations to change mobile applications, then customization capability is improved, but the need for software vendor re-implementation increases
Solution Approach 1:
Instead of modifying the original application source code, the patent creates a copy of the application configuration through metadata files. These metadata files replicate the customization information without touching the actual application code. The mobile application reads and executes these metadata files to generate customized user interfaces, effectively copying the customization state without requiring code changes.
Solution Approach 2:
The metadata files are prepared and configured in advance before the mobile application is deployed to the organization. All customization requirements are defined preliminarily in the metadata, which then guides the application's behavior. This preliminary configuration eliminates the need for ongoing vendor intervention when organizations need to customize their instances of the application.
3Reliability
If mobile applications are reconfigured when backend system changes are made, then system compatibility is maintained, but the loss of time increases
Solution Approach 1:
The metadata files are designed to be dynamic and adaptable to backend system changes. When the backend system modifies its structure or fields, the metadata can be updated to reflect these changes without requiring application reconfiguration. The mobile application reads the updated metadata and automatically adjusts its behavior, maintaining compatibility with backend changes in a dynamic, time-efficient manner.
Data Source
Figure 1A
Figure 1B
Figure 1C
AI summary
A client-based application includes sections that are used to define user interface displays for the system. The sections are customizable by a backend system so customizations are accommodated by modified versions of the mobile application.