Dynamic Containerization for Cross-Platform Mobile Apps
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Developing mobile applications that operate across multiple platforms is costly and complex due to the need for native application development, which limits cross-platform compatibility.
Innovation Solution
A dynamic containerization system that allows mobile applications to be developed using open standards like HTML5, JavaScript, and CSS, with a runtime environment on mobile devices that includes messaging libraries and a local datastore, enabling seamless operation across different platforms through plug-ins that provide additional functionalities and native device access.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If native application development is used to ensure platform-specific performance and functionality, then application reliability and native device access are improved, but device complexity and development cost increase
Solution Approach 1:
The application is segmented into a platform-independent container application and platform-specific plug-in components. The container handles core functionality while plug-ins provide platform-specific features, allowing development without deep knowledge of each mobile operating system's native requirements.
Solution Approach 2:
The patent introduces an intermediary container application that mediates between the user and platform-specific plug-ins. This container manages communication and coordination between different components, shielding developers from platform complexity while maintaining reliable native device access.
2Adaptability or versatility
If multiple native applications are developed for different platforms to ensure cross-platform compatibility, then adaptability is improved, but loss of time and development resources increase
Solution Approach 1:
The container application serves as a universal platform-independent core that can run on multiple mobile operating systems. By making the container multi-functional and platform-agnostic, the patent enables a single application to adapt to different platforms without requiring separate development efforts for each.
Solution Approach 2:
The patent performs preliminary action by pre-configuring the container application with platform-agnostic functionality and pre-defining interfaces for plug-in integration. This preliminary setup allows rapid deployment to different platforms without requiring extensive re-development or reconfiguration for each target system.
3Ease of manufacture
If platform-independent development is used to reduce development cost and time, then ease of manufacture is improved, but device complexity and access to native functions worsen
Solution Approach 1:
The system is segmented into a simple platform-independent container and separate platform-specific plug-ins. This segmentation allows the container to remain easy to develop and deploy, while complex native functionality is isolated in dedicated plug-in components that can be independently managed.
Solution Approach 2:
The container acts as an intermediary that simplifies the interface between platform-independent development and platform-specific implementation. It provides standardized mechanisms for accessing native device functions without requiring developers to directly engage with complex platform-specific APIs.
Data Source
Figure 1
Figure 2
Figure 3
AI summary
In an example embodiment, a container is downloaded, the container being an application natively executable by a first operating system of the user device, the container including: a container service including one or more libraries of functions designed by a container designer to natively operate on the first operating system; a browser; container metadata defining functions of the application, the functions compatible with the container service for the first operating system and also compatible with a container service for a second operating system; and a plug-in including one or more additional libraries of functions designed by an entity other than the container designer to perform additional native operations on the first operating system. Then, the container metadata can be executed using the browser, causing function calls to the container service and plug-in and thus controlling native functions of the user device.