Mobile App Runtime Emulating Thick-Client Apps
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Developing browser-based applications and mobile apps that replicate the functionality of non-mobile device applications is costly and complex, requiring duplicative system access mechanisms and data repositories, which consumes significant financial, time, and resource resources.
Innovation Solution
A system that includes a presentation server operating between backend systems and mobile devices, using user interface templates to provide access to non-mobile device applications' functionality and data on mobile devices, allowing for stateful network sessions and emulation of thick-client applications within mobile apps, reducing the need for duplicative resource replication.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If browser-based applications and mobile apps replicate functionality of non-mobile device applications, then access to enterprise data and functionality is enabled on mobile devices, but resource consumption and system complexity increase due to duplicative system access mechanisms and data repositories
Solution Approach 1:
A mobile application runtime environment is introduced as an intermediary layer between mobile applications and the backend system. This runtime provides stateful network sessions that enable mobile apps to access enterprise data and functionality without requiring duplicative system access mechanisms or data repositories, thereby reducing system complexity while maintaining mobile adaptability
Solution Approach 2:
The mobile application runtime environment serves multiple functions: it provides stateful network sessions for data access, emulates thick-client application behavior, and enables various mobile apps to access the same backend systems using a unified approach, eliminating the need for separate access mechanisms for different application types
2Adaptability or versatility
If browser-based applications and mobile apps replicate functionality of non-mobile device applications, then mobile access to enterprise data is enabled, but development costs and resource consumption increase
Solution Approach 1:
Instead of creating duplicative data repositories and system access mechanisms for mobile platforms, the solution copies only the necessary user interface elements and data access patterns through the mobile application runtime environment, which then leverages the existing backend system infrastructure, significantly reducing development and maintenance resources
Solution Approach 2:
The mobile application runtime environment merges the capabilities of thick-client applications with mobile device access, allowing enterprise applications to be accessed on mobile devices without replicating the full functionality or data storage of the original systems, thereby reducing resource consumption while maintaining access capability
3Reliability
If thick-client application functionality is emulated in mobile apps, then access to enterprise data and functionality is improved, but the need for duplicative resource replication increases complexity
Solution Approach 1:
The mobile application runtime environment acts as an intermediary that emulates thick-client application behavior and provides stateful network sessions to the backend system, enabling reliable access to enterprise functionality without requiring duplicative resource replication, thereby maintaining reliability while reducing complexity
Data Source
AI summary
Various embodiments herein include one or more of systems, methods, software, and data structures that are utilized in mobile app generation and execution. Such embodiments provide access to functionality and data of non-mobile device applications within mobile device apps without having to expend resources to replicate non-mobile device applications in a mobile context.