Abstract: A server-implemented method for managing packages on a client device is provided. The method initiates with receiving a content request from a client device, the content request defining a requested content item and current package data identifying one or more currently installed packages on the client device. Required packages for providing the requested content item are determined based on the content request, wherein determining the required packages includes analyzing dependencies amongst the required packages. A response to the content request is generated based on the determined required packages and the current package data, the response defining actions for providing the requested content item at the client device and actions for managing the one or more currently installed packages on the client device. The package management instructions are sent to the client device.

Abstract: 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.

Abstract: A server-implemented method for managing packages on a client device is provided. The method initiates with receiving a content request from a client device, the content request defining a requested content item and current package data identifying one or more currently installed packages on the client device. Required packages for providing the requested content item are determined based on the content request, wherein determining the required packages includes analyzing dependencies amongst the required packages. a response to the content request is generated based on the determined required packages and the current package data, the response defining actions for providing the requested content item at the client device and actions for managing the one or more currently installed packages on the client device. The package management instructions are sent to the client device.

Abstract: A hybrid application is provided. 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.