Hybrid Mobile App Transformation via Runtime Data Translation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Mobilizing large-scale enterprise web applications to mobile platforms is inefficient due to incompatibility of data configurations, requiring extensive manual changes and increasing development costs and time.
Innovation Solution
A framework that abstracts web application data service configurations into metadata, generates a transformation mapping database, and packages a hybrid mobile app with a UI library and runtime translator to automatically transform web apps into mobile-compatible apps without altering the source code.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If manual configuration changes are performed to make web apps compatible with mobile landscape, then compatibility with mobile devices is improved, but development cost and time increase significantly
Solution Approach 1:
The patent introduces a runtime translator as an intermediary component that automatically translates data service configuration calls from web apps (designed for cloud/on-premise landscapes) to mobile landscape configurations. This translator runs within the hybrid mobile app container and mediates between the web app's data service requests and the mobile platform's data services, eliminating the need for manual configuration changes while maintaining compatibility.
Solution Approach 2:
The patent transforms the data service configuration parameters automatically through the runtime translator. The translator intercepts configuration parameters intended for cloud/on-premise landscapes and dynamically transforms them into appropriate mobile landscape parameters, allowing the same web app to run on mobile devices without manual reconfiguration.
2Adaptability or versatility
If extensive development effort is applied to ensure all apps are compatible with mobile landscape, then compatibility is improved, but development cost increases
Solution Approach 1:
The runtime translator serves as a cost-effective intermediary that handles all configuration translation automatically. Instead of requiring developers to manually adapt each app's configuration, the translator provides a centralized, automated solution that works across all apps in the enterprise system, significantly reducing development costs.
Solution Approach 2:
The runtime translator is designed as a universal component that can translate configurations for multiple different web apps simultaneously. This multi-functional approach allows a single solution to serve numerous apps across different business scenarios and personas, reducing the overall development cost for enterprise-wide mobile deployment.
3Adaptability or versatility
If manual configuration changes are performed for each web app, then individual app compatibility is improved, but overall transformation time increases
Solution Approach 1:
The runtime translator enables immediate deployment of web apps to mobile platforms without time-consuming manual configuration changes. The automatic translation occurs at runtime, allowing apps to be transformed and deployed rapidly while maintaining full compatibility through the translator's intervention.
Solution Approach 2:
The framework performs preliminary packaging of the web app with the runtime translator and transformation mapping database during the build process. This preliminary action prepares the app for mobile deployment in advance, so that at runtime, the translation happens automatically without requiring additional time for configuration changes.
4Stability of the object's composition
If web apps inherit cloud or on-premise data configurations, then existing functionality is preserved, but compatibility with mobile devices is lost
Solution Approach 1:
The runtime translator acts as an intermediary layer that preserves the original cloud/on-premise data configuration calls in the web app while simultaneously adapting them to work with mobile landscape data services. This allows the app to maintain its existing functionality and configuration structure while achieving mobile device compatibility through the translator's mediation.
Solution Approach 2:
The framework creates a copy of the data service configuration translation capability within the runtime translator. Instead of modifying the original web app's configuration, the translator creates and executes translated versions of configuration calls, preserving the original functionality while enabling mobile compatibility.
Data Source
AI summary
Described herein is a framework for transforming a web application (App) into a hybrid mobile App. The framework is used in a process for generating a hybrid mobile App package in a container, such as a Cordova container. The hybrid mobile App package includes a transformation interface with a transformation mapping database which provides a one-to-one mapping of data services utilized by the transformed hybrid mobile App. During runtime, a runtime interface retrieves the data configuration information of the hybrid mobile App based on the transformation mapping database. As such, the transformation is achieved without modifying source code of the original web App.