Hybrid applications
A native application portion is configured for execution in a native environment. A native kernel is defined in the native environment, the native kernel including one or more native plugin services accessible by the native application portion. A non-native application portion is configured for execution in a web view context. A non-native kernel is defined in the web view context, the non-native kernel including one or more non-native plugin services accessible by the non-native application portion. A native kernel bridge service is interfaced with the native kernel, and a non-native kernel bridge service is interfaced with the non-native kernel. The native kernel bridge service and non-native kernel bridge service are interfaced with each other, enabling the non-native application portion to access the native plugin services of the native kernel, and enabling the native application portion to access the non-native plugin services of the non-native kernel.
1. A hybrid application configured for execution by a processor of a computing device, comprising:
a native application portion configured for execution in a native environment of the computing device;
a native kernel defined in the native environment, the native kernel including one or more native plugin services accessible by the native application portion;
a non-native application portion configured for execution in a web view context of the computing device;
a non-native kernel defined in the web view context, the non-native kernel including one or more non-native plugin services accessible by the non-native application portion;
a native kernel bridge service interfaced with the native kernel;
a non-native kernel bridge service interfaced with the non-native kernel;
wherein the native kernel bridge service and the non-native kernel bridge service are interfaced with each other, and enable the non-native application portion to access the native plugin services of the native kernel, and enable the native application portion to access the non-native plugin services of the non-native kernel;
wherein one or more of the native plugin services or the non-native plugin services provides a user interface for the hybrid application.
2. The hybrid application of claim 1 , wherein the web view context is defined by a native web browser application of the computing device.
3. The hybrid application of claim 1 , wherein the access to the native plugin services and the non-native plugin services by either of the native application portion or the non-native application portion occurs via a common API.
4. The hybrid application of claim 1 , wherein the non-native application portion is defined by a model view controller or an application framework.
5. The hybrid application of claim 1 , wherein one or more of the native plugin services provides access to a native feature of the computing device.
6. The hybrid application of claim 1 , wherein one or more of the non-native plugin services accesses a cloud-based service.
7. A hybrid application configured for execution by a processor of a computing device, comprising:
a native application portion configured for execution in a native environment of the computing device;
a native kernel defined in the native environment, the native kernel including one or more native plugin services accessible by the native application portion;
a non-native application portion configured for execution in a web view context of the computing device;
a non-native kernel defined in the web view context, the non-native kernel including one or more non-native plugin services accessible by the non-native application portion;
a native kernel bridge service interfaced with the native kernel;
a non-native kernel bridge service interfaced with the non-native kernel;
wherein the native kernel bridge service and the non-native kernel bridge service are interfaced with each other, and enable the non-native application portion to access the native plugin services of the native kernel, and enable the native application portion to access the non-native plugin services of the non-native kernel;
a frame context defined within the web view context;
a second non-native application portion defined within the frame context;
a bridge client defined within the frame context, the bridge client configured to receive an API call from the second non-native application portion for one of the native plugin services or the non-native plugin services, and forward the API call to the non-native bridge service.
8. The hybrid application of claim 7 , wherein the bridge client is configured to restrict access of the second non-native application portion to a subset of the non-native plugin services of the non-native kernel.
9. The hybrid application of claim 7 , wherein the bridge client is configured to restrict access of the second non-native application portion to a subset of the native plugin services of the native kernel.
10. The hybrid application of claim 7 , wherein the second non-native application portion is defined by a model view controller or an application framework.
11. The hybrid application of claim 7 , further comprising,
a nested frame context defined within the frame context;
a third non-native application portion defined within the nested frame context;
a second bridge client defined within the nested frame context, the second bridge client configured to receive an API call from the third non-native application portion for one of the native plugin services or the non-native plugin services, and forward the API call to the bridge client.
12. A hybrid application configured for execution by a processor of a computing device, comprising:
a native application portion configured for execution in a native environment of the computing device;
a native kernel defined in the native environment, the native kernel including one or more native plugin services accessible by the native application portion;
a native kernel bridge service defined in the native environment and interfaced with the native kernel;
a non-native application portion defined in a first web view context of the computing device;
a non-native kernel defined in a second web view context of the computing device, the non-native kernel including one or more non-native plugin services accessible by the non-native application portion;
a non-native kernel bridge service defined in the second web view context and interfaced with the non-native kernel;
wherein the native kernel bridge service and the non-native kernel bridge service are interfaced with each other, and enable the non-native application portion to access the native plugin services of the native kernel, and enable the native application portion to access the non-native plugin services of the non-native kernel;
a frame context defined within the second web view context;
a second non-native application portion defined within the frame context;
a bridge client defined within the frame context, the bridge client configured to receive an API call from the second non-native application portion for one of the native plugin services or the non-native plugin services, and forward the API call to the non-native bridge service.
13. The hybrid application of claim 12 , wherein the web view context is defined by a native web browser application of the computing device.
14. The hybrid application of claim 12 , wherein the access to the native plugin services and the non-native plugin services by either of the native application portion or the non-native application portion occurs via a common API.
15. The hybrid application of claim 12 , wherein the non-native application portion is defined by a model view controller or an application framework.
16. The hybrid application of claim 12 , further comprising,
a nested frame context defined within the frame context;
a third non-native application portion defined within the nested frame context;
a second bridge client defined within the nested frame context, the second bridge client configured to receive an API call from the third non-native application portion for one of the native plugin services or the non-native plugin services, and forward the API call to the bridge client.