Abstract: A native user interface (UI) application of a mobile device includes a library of different components such as text, forms, tables, lists, maps, views and buttons. The components can also have associated actions in some cases. When a view of the UI is launched, the mobile device contacts a server or other data source to obtain metadata associated with the view. The metadata can be tailored to a user or organization of the mobile device. The metadata selects specific components and defines a layout for the components. The mobile device uses the metadata to retrieve the components and render them in the view. The views can be changed by changing the metadata without changing the native application.

Abstract: An approach is proposed to support version control for integrating updated web-based components with a native application of a mobile device. A new version of a mini app is received at an application version control module configured to control versioning of the mini app and the native application, wherein the mini app includes one or more web-based features in JavaScript to be integrated with the native application. Version compatibility checks are performed to confirm that the new version of the mini app only contains native dependencies that match with a version of the native application the version of the mini app depends on. The new version of the mini app is integrated with the native application into the target mobile application if the version compatibility checks pass. Finally, the target mobile application is uploaded to an app store to make the target mobile application available to an end user.

Abstract: An approach is proposed to support version control for integrating updated web-based components with a native application of a mobile device. A new version of a mini app is received at an application version control module configured to control versioning of the mini app and the native application, wherein the mini app includes one or more web-based features in JavaScript to be integrated with the native application. Version compatibility checks are performed to confirm that the new version of the mini app only contains native dependencies that match with a version of the native application the version of the mini app depends on. The new version of the mini app is integrated with the native application into the target mobile application if the version compatibility checks pass. Finally, the target mobile application is uploaded to an app store to make the target mobile application available to an end user.

Abstract: An approach is proposed to support cross-platform information exchange mechanism for integration of web-based components with a native application. First, mini apps are imported to a platform of a mobile device, wherein the mini apps are web-based features assembled and packaged together in JavaScript to be deployed to and integrated with the application native to the platform. A bridge enables bi-directional communication between the mini apps in JavaScript and the native to the platform by marshalling native code of the native application into a JavaScript project to be integrated with the imported mini apps and un-marshalling the mini apps in JavaScript to the native code of the native application. The mini apps are then integrated with the native application on the mobile device over the bridge to create a target mobile application, which is uploaded to an app store to make the target mobile application available to an end user.

Abstract: An approach is proposed to support automatic API generation for integration of web-based components with a native application. First, mini apps are included in a container, wherein the mini apps are web-based features assembled together as a bundle of JavaScript assets to be integrated with the native application on a mobile device. A set of APIs to the mini apps are then automatically generated based on pre-defined schemas in native code specific to the platform of the mobile device and merged with the mini apps into the container. The container is published to a repository at a central, team shared, location and imported to the mobile device for integration with the native application. Finally, a target mobile application is created by integrating the mini apps with the native application on the mobile device via the APIs, wherein the target mobile application is uploaded and made available to an end user.