Mobile App Framework Configuration Updates
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Mobile application development requires recompilation and redistribution for minor changes, such as user interface updates, which is inefficient and time-consuming.
Innovation Solution
A mobile application framework that allows for customization and extensibility through configuration files, enabling updates to user interface elements and metadata without recompiling the application, using a mobile platform server to deploy changes directly to end-users.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If the application is recompiled and uploaded to the app store for minor changes, then the application can be updated, but the development time and deployment efficiency deteriorate
Solution Approach 1:
The application is segmented into two independent parts: the compiled application code (uploaded to app store) and the configuration data (stored separately on server). This segmentation allows the configuration portion to be updated independently without requiring recompilation and re-upload of the entire application, thus resolving the time loss contradiction.
Solution Approach 2:
The configuration data is extracted from the compiled application and stored separately on a remote server. This extraction enables the configuration to be modified and deployed independently from the application binary, eliminating the need to recompile and re-upload the application for configuration changes, thereby reducing development and deployment time.
2Manufacturing precision
If the application is recompiled for every update, then the application remains current, but developer productivity deteriorates
Solution Approach 1:
By segmenting the application into immutable compiled code and mutable configuration data, developers can update configuration without triggering the recompilation process. This maintains update accuracy while significantly improving productivity by eliminating repetitive build cycles.
Solution Approach 2:
The application is prepared in advance with embedded configuration retrieval functionality that points to the remote server. This preliminary setup allows future configuration changes to be deployed immediately without requiring preliminary recompilation actions, thus enhancing developer productivity.
3Stability of the object's composition
If configuration data is stored locally in the application, then the application is self-contained, but update flexibility deteriorates
Solution Approach 1:
Configuration data is extracted from the local application storage and relocated to a remote server. This extraction maintains the application's structural integrity by keeping the compiled code self-contained while enabling flexible configuration updates through external data retrieval, thus resolving the contradiction between stability and adaptability.
Solution Approach 2:
A remote server acts as an intermediary between the application and the configuration data. The application maintains stable local structure while communicating with the external server to retrieve updated configurations, thereby achieving both structural integrity and update flexibility.
Data Source
AI summary
In an example embodiment, one or more configuration files are defined for an extensible application, the one or more configuration files including metadata for the extensible application. Then code defining behavior of the extensible application is combined with a mobile application framework, the mobile application framework including a data component configured to obscure details of an underlying data source for the extensible application, the code including calls made to one or more of the generic components. The code is compiled and one or more of the configuration files can be uploaded to a mobile platform server for storage. Then the compiled code is uploaded to a platform server for distribution to one or more devices. One or more of the configuration files is configured to alter an aspect of the extensible application. Finally, the altered one or more configuration files is uploaded to the mobile platform server for storage.