Client-Side Server Bridge for Cross-Platform Native Access
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Developing web-application code that can execute on multiple devices with different native layers while accessing native features and maintaining performance is challenging due to the limitations of cross-platform layers being farther from hardware and software resources, leading to poor performance and inability to utilize advanced features like gyroscope or camera access.
Innovation Solution
A method is implemented where cross-platform application code is executed on a client device, determining whether to invoke native or cross-platform APIs based on performance, efficiency, and feature capabilities, using a bridge to access native features and deploying native code specific to each device, allowing access to native features from a common cross-platform programming environment.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If web-application code is developed for the cross-platform layer, then the code can execute on multiple devices with different native layers, but the performance is poor and access to native features is limited
Solution Approach 1:
The patent introduces a bridge as an intermediary layer between the cross-platform layer and native layer. The bridge enables the cross-platform application code to access native features and resources by translating cross-platform API calls into native API calls, thus maintaining cross-platform compatibility while achieving native-level performance and feature access.
2Adaptability or versatility
If web-application code is developed for the cross-platform layer, then the code can execute on multiple devices, but the level of performance is poor relative to native layer implementation
Solution Approach 1:
The bridge acts as a mediator that enables fast native code execution while maintaining cross-platform compatibility. By routing performance-critical operations through the bridge to native implementations, the system achieves execution speeds comparable to native applications while preserving the ability to run on multiple platforms.
3Adaptability or versatility
If web-application code is developed for the cross-platform layer, then the same code can run on multiple devices, but access to native features such as gyroscope, accelerometer, camera, and video camera is not supported
Solution Approach 1:
The bridge serves as an intermediary that translates cross-platform feature requests into native feature access. When the application code needs to access native features like camera or gyroscope, the bridge intercepts these requests and routes them to the appropriate native APIs, enabling feature access while maintaining cross-platform code compatibility.
4Ease of manufacture
If web-application code is developed for the cross-platform layer, then deployment is simplified, but the ability to draw advanced, complex, or three-dimensional animations is limited
Solution Approach 1:
The bridge enables advanced graphics capabilities by routing rendering operations to native graphics engines. Cross-platform application code can request complex animations and 3D rendering through the bridge, which then utilizes the device's native graphics hardware and APIs to deliver high-quality visual output while keeping the application logic portable across platforms.
Data Source
AI summary
A method of executing a cross-platform application on a system is disclosed. An instruction pertaining to an execution of the cross-platform application on the system is received. Based on a determination that the instruction pertains to a rendering of an element of a user interface of the cross-platform application on the system, the instruction is sent across a bridge to an engine executing in the native layer to process the instruction at the native layer. Alternatively, based on a determination that the instruction does not pertain to a rendering of the element of the user interface of the cross-platform application on the system, the instruction is sent to an engine executing in the cross-platform layer of the system to process the instruction at the cross-platform layer.