UI Change Condenser for Reducing Application Startup Latency
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional user interface applications experience long startup times due to the application of numerous UI changes, which are saved and loaded during initialization, frustrating users with prolonged waiting periods.
Innovation Solution
A system that condenses UI changes into a smaller, redundant-free set, allowing for efficient processing and application during the loading of the UI application, reducing the number of changes and thereby decreasing startup time.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If all UI changes are collected and applied to the UI application during startup, then the UI application reflects all modifications, but the startup time becomes excessively long
Solution Approach 1:
The patent extracts only the necessary UI changes from the complete set of changes. The system identifies and applies only those UI changes that are relevant to the current user context, role, and configuration, rather than applying all changes indiscriminately. This extraction process eliminates redundant changes and significantly reduces the number of changes that need to be processed during startup.
Solution Approach 2:
The patent segments the complete set of UI changes into multiple categories and subsets based on user roles, configurations, and relevance. Changes are divided into different groups (e.g., role-specific changes, configuration-specific changes, common changes) and applied in a structured manner. This segmentation allows the system to process and apply changes more efficiently by handling them in organized batches rather than as a monolithic set.
2Adaptability or versatility
If numerous UI changes are loaded during initialization, then all modifications are preserved, but user waiting time increases
Solution Approach 1:
The patent applies partial action by loading and applying only the necessary subset of UI changes required for the current user context, rather than loading all possible changes. The system determines the minimum required changes based on user role, configuration, and access rights, and applies only those changes. This approach maintains full UI adaptability while significantly reducing the loading burden and startup time.
Solution Approach 2:
The patent performs preliminary analysis and filtering of UI changes before the actual application process. The system pre-processes the change set by identifying relevant changes, organizing them by priority and category, and preparing them for efficient application. This preliminary action ensures that when startup occurs, the system is ready to apply changes quickly without unnecessary processing overhead.
3Reliability
If complete UI change sets are applied, then all user modifications are reflected, but processing overhead increases
Solution Approach 1:
The patent applies local quality by tailoring the UI change application process to specific user contexts, roles, and configurations. Different subsets of changes are applied to different user groups based on their specific needs and permissions. This localized approach ensures that each user receives the appropriate changes for their context while avoiding the processing overhead of applying all changes to every user. The system maintains accuracy by ensuring that the right changes are applied to the right users.
Data Source
AI summary
Systems and methods provide reception of a request from a client system for a user interface (UI) application, identification of a plurality of UI changes associated with the UI application and comprising one or more non-index-related UI changes and one or more index-related UI changes, each of the one or more non-index-related UI changes associated with a UI node and a UI node characteristic, and each of the one or more index-related UI changes associated with a UI node index, sorting of each of the one or more non-index-related UI changes based on associated UI node and UI node characteristic, condensing of non-index-related UI changes associated with each UI node characteristic of each UI node to zero or one UI changes associated with each UI node characteristic of each UI node, condensing of each of the one or more index-related UI changes to less than the one or more index-related UI changes based the UI node indices, and transmission of the UI application, the condensed non-index-related UI changes and the condensed index-related UI changes to the client system.


