Building Block Metadata Linkage for Application Customization
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Users face challenges in customizing applications created by application providers, as customizations are often overridden when the application is modified, leading to a complex and burdensome process of re-customizing to maintain the desired look and feel and settings.
Innovation Solution
The system allows users to create applications using linkable building blocks with customizable metadata, enabling users to define new building blocks by mapping I/O features of existing blocks, and providing a user interface for selecting and combining these blocks without modifying the underlying application metadata, thus allowing selective customization and preservation of user preferences.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If users customize applications created by application providers, then user preferences and settings are improved, but customizations are overridden when the application is modified
Solution Approach 1:
The system segments the application into two distinct layers: the base application layer (provided by the application provider) and the customization layer (created by users through building blocks). This segmentation allows customizations to be stored separately as metadata associated with specific building blocks, preventing them from being overridden when the base application is modified or updated.
Solution Approach 2:
The patent introduces metadata as an intermediary layer between the base application and user customizations. This metadata stores customization information and is linked to building blocks, acting as a buffer that preserves user preferences even when the underlying application changes. The metadata serves as the mediator that maintains the connection between the application structure and user-specific modifications.
2Adaptability or versatility
If users re-customize applications after modifications, then customizations are restored, but the process becomes complex and burdensome
Solution Approach 1:
The system performs preliminary action by automatically preserving customization metadata when the application is first customized. Instead of requiring users to manually save or export their customizations, the system proactively stores the customization state in metadata associated with building blocks, making the restoration process automatic and eliminating the need for complex re-customization procedures.
Solution Approach 2:
The patent implements a copying mechanism where customization metadata is replicated and stored alongside the building block definitions. When the application is updated, the system automatically copies the preserved metadata back to the building blocks, enabling seamless restoration of customizations without requiring users to manually recreate them, thus simplifying the process significantly.
3Adaptability or versatility
If users create new building blocks with metadata, then application flexibility is improved, but the system complexity increases
Solution Approach 1:
The patent creates a universal building block framework where a single metadata structure can serve multiple purposes: storing customization preferences, defining building block relationships, and managing application configuration. This multi-functionality reduces the need for separate complex systems for each purpose, as the metadata infrastructure handles diverse requirements through a unified approach, thereby limiting the increase in system complexity.
Data Source
AI summary
Systems and methods relate to creating applications using building blocks linked together with metadata. A user interface can enable a user to create an application. Creating the application can include defining a new building block configured to generate output data. The new building block can include one or more existing building blocks and the metadata associated with the existing building blocks. For example, a building block can include at least one input/output (I/O) feature configured to receive inputs and/or generate outputs. Further, the existing building block can correspond to a data structure including external I/O features. The new building block can be linked to an existing building block by mapping an external I/O feature of the existing building block to an open I/O feature of the new building block. The mapping can be stored in metadata associated with the new building block.