Abstract: Described is a system, method, and computer-implemented apparatus for deploying and updating toolkits in hybrid cloud-local development platforms. In one embodiment, a cloud based software development environment is connected with a local development environment, enabling the cloud based software development environment (cloud environment) to inquire into the toolkit versions installed on the local machine. Once missing or incompatible versions of toolkits are identified, the cloud environment uses the connector module to instruct the local machine to download and install the appropriate toolkit version. The connector may use any types of bi-directional communication channels, such as a browser plugin, a web server hosted on the local machine, web services, or the like.

Abstract: Described is a system, method, and computer-implemented apparatus for deploying and updating toolkits in hybrid cloud-local development platforms. In one embodiment, a cloud based software development environment is connected with a local development environment, enabling the cloud based software development environment (cloud environment) to inquire into the toolkit versions installed on the local machine. Once missing or incompatible versions of toolkits are identified, the cloud environment uses the connector module to instruct the local machine to download and install the appropriate toolkit version. The connector may use any types of bi-directional communication channels, such as a browser plugin, a web server hosted on the local machine, web services, or the like.

Abstract: Described herein is a framework for transforming a web application (App) into a hybrid mobile App. The framework is used in a process for generating a hybrid mobile App package in a container, such as a Cordova container. The hybrid mobile App package includes a transformation interface with a transformation mapping database which provides a one-to-one mapping of data services utilized by the transformed hybrid mobile App. During runtime, a runtime interface retrieves the data configuration information of the hybrid mobile App based on the transformation mapping database. As such, the transformation is achieved without modifying source code of the original web App.

Abstract: A framework for building applications is described herein. In accordance with one aspect, App metadata of an App may be specified by a user. The App metadata includes configuration information of the App. The App metadata and build rules may be input into a pre-build module to generate build scripts for building the App. The build scripts may be based on the App metadata and build rules. The build scripts may be provided to a build module to build the App for deployment.

Abstract: A framework for enabling mobile functionality in a web application (App) to produce a mobile enabled App is described herein. In accordance with one aspect, a web App and a configuration file is provided to a mobile application (mApp) enabler. The configuration file contains configuration information for mobile enablement. The mApp enabler changes a project structure of the web App to a mobile structure and inserts bootstrap codes into the web App. The bootstrap codes load plugins for mobile devices. Codes to handle events available on mobile devices may be inserted, and data sources for the web App may be converted to data sources for a mobile enabled App to enable the web App for mobile (mobile enabled web App).

Abstract: A framework for developing web and hybrid applications (Apps) of a project is described herein. In accordance with one aspect, a façade framework is provided. The façade framework includes a web library having a set of application program interfaces (APIs) of hybrid features of a mobile device, a hybrid library having a set of APIs of hybrid features of a mobile device, and a unified interface for interfacing with the web and hybrid libraries. Base code of a base project may be provided using an application development system. The base code may include common code to web assets common to the web and hybrid Apps of the project. The base code may be extended using the application development system to produce an extended code of the project, where the extended code includes hybrid features used by the project. The unified interface provides APIs from the web and hybrid libraries used by the project.

Abstract: A framework for enabling mobile functionality in a web application (App) to produce a mobile enabled App is described herein. In accordance with one aspect, a web App and a configuration file is provided to a mobile application (mApp) enabler. The configuration file contains configuration information for mobile enablement. The mApp enabler changes a project structure of the web App to a mobile structure and inserts bootstrap codes into the web App. The bootstrap codes load plugins for mobile devices. Codes to handle events available on mobile devices may be inserted, and data sources for the web App may be converted to data sources for a mobile enabled App to enable the web App for mobile (mobile enabled web App).

Abstract: A framework for developing web and hybrid applications (Apps) of a project is described herein. In accordance with one aspect, a façade framework is provided. The façade framework includes a web library having a set of application program interfaces (APIs) of hybrid features of a mobile device, a hybrid library having a set of APIs of hybrid features of a mobile device, and a unified interface for interfacing with the web and hybrid libraries. Base code of a base project may be provided using an application development system. The base code may include common code to web assets common to the web and hybrid Apps of the project. The base code may be extended using the application development system to produce an extended code of the project, where the extended code includes hybrid features used by the project. The unified interface provides APIs from the web and hybrid libraries used by the project.

Abstract: A framework for building applications is described herein. In accordance with one aspect, App metadata of an App may be specified by a user. The App metadata includes configuration information of the App. The App metadata and build rules may be input into a pre-build module to generate build scripts for building the App. The build scripts may be based on the App metadata and build rules. The build scripts may be provided to a build module to build the App for deployment.