UI Component Similarity Comparison for Storage Reduction

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Cloud platforms face inefficiencies due to the storage and maintenance of numerous UI components with similar characteristics, leading to memory and storage wastage, increased maintenance overhead, and degraded runtime performance.

Innovation Solution

A system that generates a data structure representing each UI component as a tree, where each characteristic is represented in a leaf node, and calculates a similarity score between components. If the similarity score meets a threshold, the system displays a message to preferentially implement one component over another or to reuse existing components instead of developing new ones.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If multiple UI components with similar characteristics are stored and maintained, then component functionality and versatility are improved, but memory and storage requirements increase significantly

Engineering Contradiction:

Improvecomponent functionalityVSAvoidmemory and storage requirements

Core Design Contradiction:

Adaptability or versatilityVSQuantity of substance

Solution Approach 1:

The patent merges similar UI components by identifying them through characteristic comparison and consolidating them into a single canonical component. The system compares characteristics of components, determines similarity, and merges duplicate or near-duplicate components, thereby reducing the total number of components stored while maintaining functional versatility through the unified component design.

Inventive Principle:

Principle #5Merging (Combining)

Solution Approach 2:

The patent creates universal component templates that can serve multiple functions. By extracting common characteristics and creating a canonical representation, the system enables a single component design to fulfill roles previously requiring multiple specialized components, thus reducing storage requirements while maintaining adaptability.

Inventive Principle:

Principle #6Universality (Multi-functionality)

2Reliability

If numerous UI components with similar characteristics are maintained, then component availability is improved, but maintenance overhead increases significantly

Engineering Contradiction:

Improvecomponent availabilityVSAvoidmaintenance overhead

Core Design Contradiction:

ReliabilityVSDevice complexity

Solution Approach 1:

The system merges components with similar characteristics into a single canonical component, reducing the number of components that require maintenance. By consolidating maintenance efforts onto fewer unified components, the system maintains component availability while significantly reducing maintenance overhead and complexity.

Inventive Principle:

Principle #5Merging (Combining)

Solution Approach 2:

Instead of maintaining multiple original components, the system creates a canonical component and uses it as a template. When new components are needed, the system generates them by copying or instantiating the canonical component with specific parameter values, thereby reducing maintenance scope while ensuring component availability through the template pattern.

Inventive Principle:

Principle #26Copying

3Adaptability or versatility

If all UI components are downloaded at runtime, then component functionality is ensured, but runtime performance degrades due to unnecessary downloads

Engineering Contradiction:

Improvecomponent functionalityVSAvoidruntime performance

Core Design Contradiction:

Adaptability or versatilityVSProductivity

Solution Approach 1:

The patent extracts and compares only the essential characteristics of UI components rather than loading complete component definitions. By extracting characteristic data (such as visual properties, behavioral attributes, and structural information) and comparing these extracted features, the system determines component similarity without downloading full component implementations, thereby improving runtime performance while ensuring functionality through characteristic-based identification.

Inventive Principle:

Principle #2Taking out (Extraction)

Solution Approach 2:

The system performs preliminary characteristic extraction and comparison before runtime component loading. By pre-comparing characteristics and identifying similar components in advance, the system can optimize component selection and loading strategies at runtime, avoiding unnecessary downloads and improving performance while maintaining component functionality.

Inventive Principle:

Principle #10Preliminary action

Data Source

PatentUS20250028735A1Component characteristics similarity comparison

Publication Date: 2025.01.23 SALESFORCE INC

AI summary

Techniques described herein support component maintenance that accounts for a similarity between characteristics of different components. To identify components with similar characteristics, one or more techniques described herein support generation of a data structure (e.g., a tree) that represents a component, where each characteristic may be represented in a different leaf node. The system may generate a similarity score, or value (e.g., as a percentage), between multiple components based on comparing individual nodes of a tree representing each component, respectively. If the similarity score satisfies a threshold, then the system may display, at the UI, a message indicating to a user to preferentially implement one component over another.