Software Installation Customization Retention
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional software update processes often result in the loss of customization efforts for manufacturers and service providers, as updates overwrite existing code, leading to the need for re-customization, which is time-consuming and resource-intensive, especially with rapid changes in programming languages.
Innovation Solution
The system provides a method to retain and modify customer user interface customization during software updates by allowing installers to select, move, and add software components graphically through an API, enabling the porting of existing software attributes and the inclusion of proprietary components, thus maintaining branding and aesthetics.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If software updates are installed using conventional methods, then software functionality is updated, but customization is lost due to code overwriting
Solution Approach 1:
The software is divided into separate components: core functionality code and customization code. The customization code is extracted and stored independently in a configuration file or database, allowing it to be preserved separately from the core software updates. This segmentation enables selective updating of functionality without affecting customizations.
Solution Approach 2:
An intermediary layer (configuration file, database, or metadata structure) is introduced between the core software code and the customization elements. This intermediary stores customization parameters and allows the installation process to reference and preserve them during updates, acting as a buffer that prevents direct overwriting of customization data.
2Loss of information
If manufacturers re-customize user interfaces after software updates, then branding is restored, but time and resources are consumed
Solution Approach 1:
The system performs preliminary actions by automatically detecting and preserving customization parameters before the software update installation occurs. The customization data is extracted and stored in advance, so when the update is applied, the branding and customizations are automatically restored without requiring manual re-customization efforts after installation.
Solution Approach 2:
The installation process is designed to be self-service regarding customizations. The system automatically detects existing customizations, preserves them during the update process, and restores them after installation without requiring external manual intervention. This eliminates the need for manufacturers to manually re-customize interfaces after every update.
3Adaptability or versatility
If software updates overwrite existing code, then new features are installed, but existing customization parameters are lost
Solution Approach 1:
The software architecture is segmented into core functional components and customization parameter components. During updates, only the core functional components are overwritten, while the customization parameters stored in separate configuration files or databases remain intact. This allows new features to be installed while preserving existing customization settings.
Solution Approach 2:
An intermediary storage mechanism (configuration file, database, or metadata layer) is used to store customization parameters separately from the executable code. This intermediary acts as a protective layer that prevents customization data from being overwritten during software updates, allowing the update process to modify core functionality without affecting stored customization parameters.
Data Source
AI summary
The present invention facilitates customizing software installation such as software updates for a user interface (UI) of a mobile communication device. The systems and methods of the present invention utilize a component that receives software updates (e.g., releases, releases, patches, upgrades, etc.) and presents various installation options to an installer through an interface. The installer can interact with the interface to select one or more components (e.g., controls, menus, menu items, etc) to install and define how such components are installed. For example, the installer can determine a control's location with respect to other controls within a user interface. This can be achieved by moving graphical components within the user interface and/or by providing parameters, setting flags, and/or including suitable arguments. In addition, the installer can add components to an installation. For example, the installer can add proprietary and/or third party applications, features, brands, logos and aesthetics to the installation.