Smart Mobile Client Architecture for Offline Enterprise App Updates
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing mobile application development methods require frequent re-installation of applications for updates, restrict offline usage, and fail to fully leverage device capabilities, leading to inefficiencies and increased costs due to the need for continuous data connections and installation upgrades.
Innovation Solution
A metadata-driven architecture with a proprietary message structure allows a smart mobile client to update user interface and business logic without re-installation, enabling applications to run natively offline and utilize device features by segregating UI elements from data elements, reducing data exchange and bandwidth requirements.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If traditional mobile application deployment methods are used, then applications can be delivered to mobile devices, but frequent re-installation is required for updates and new applications
Solution Approach 1:
The patent segments the mobile application into separate components: a core runtime environment that remains on the device and updateable application modules that can be independently deployed. This allows updates to be applied without requiring complete re-installation of the application
Solution Approach 2:
The patent implements preliminary action by pre-installing a runtime environment and framework on the mobile device that enables future application updates without re-installation. This preliminary infrastructure allows subsequent application modules to be deployed and updated in place
2Adaptability or versatility
If applications are designed for online mode only, then server-side processing capabilities are utilized, but offline usage is disabled
Solution Approach 1:
The patent segments application functionality into online-dependent features and offline-capable features. The runtime environment separates data synchronization operations from core application logic, allowing the application to function offline while maintaining the ability to synchronize when connected
Solution Approach 2:
The patent introduces a local database and cache mechanism as an intermediary between the application and the server. This intermediary allows the application to read and write data locally offline, then synchronize changes with the server when connectivity is available, maintaining reliability in both online and offline modes
3Productivity
If complete application packages are transferred over networks, then applications can be deployed, but data bandwidth requirements are high
Solution Approach 1:
The patent extracts the common runtime environment and framework from each application package, placing it once on the device. Only the specific application logic and data are transferred over the network, significantly reducing bandwidth requirements while maintaining deployment efficiency
Solution Approach 2:
The patent creates a universal runtime environment that can host multiple different applications. This single runtime infrastructure serves multiple applications, eliminating the need to transfer redundant framework and library files with each application deployment
4Productivity
If application updates require user intervention for installation, then version control is maintained, but user effort and costs increase
Solution Approach 1:
The patent implements self-service by enabling the mobile device and runtime environment to automatically receive, validate, and install application updates without requiring user intervention. The system autonomously manages the update process while maintaining version control and integrity checks
Data Source
AI summary
The embodiments herein relate to a method and system for design and deployment of cross platform native mobile enterprise applications. Multiple versions of the same application need not be installed repeatedly instead the existing version can be updated. Mobile Applications User Interface and Business Logic are recognized by a smart mobile client (specific for each operating system), which allows changes to User interface and business logic to be pushed from the application management server to the client without need for re-installation. Information between Mobile Server and smart client is exchanged using a proprietary message structure, which has been developed to build complex mobile application. A smart interpreter interprets and parses the application while also rendering it at run time. The smart mobile client has pre-built ability to use native mobile device features and support for offline storage and synchronization with the mobile server.