Systems and methods are provided to test changes for a mobile app built by web-based tooling directly on a physical mobile device. A first application can be loaded on a mobile device. The first application can receive metadata of a second application. The first application can execute the second application using the metadata. Access to local resources can be intercepted and redirected to the server for processing. Additionally, changes made to the second application using the web-based tooling can be pushed to the first application using a persistent channel allowing the changes to be immediately tested.

Efficient means to test server generated applications on mobile device

Systems and methods are provide for optimizing the iOS application build process to dramatically reduce build times for highly templated mobile applications. A request to build a first application developed using an application development framework can cause one or more binary artifacts of a second application compiled using a build toolkit to be determined. Declarative information associated with the one or more binary artifacts of the second application can be then modified using metadata associated with the first application. The metadata configures one or more components included in the first application. The first application can then be built to target a mobile device using the one or more binary artifacts of the second application and the modified declarative information.

High performant ios template based application build system

For cloud development tools building native mobile applications, it is often useful to test out parts of an application on a physical device. Systems and methods are provide for providing an native application that allows portions of itself to uptake newly developed features allowing rapid testing of these features.

Updatable native mobile application for testing new features

Systems and methods are provided for allowing end users to intuitively databind functional components to backend services through visual affordances. Each UI component can advertise which sections of the UI can be independently databound to individual properties coming from data of backend services. When the user wishes to databind a UI component, the sections of the UI that can be databound now transforms to show relevant text describing the function of that particular section. The user can be presented with a databinding interface that consistent of all the possible pieces of data that the user can bind to as well as visual slots that map to the slots in the visual preview. To databind a component, a user can drag and drop the particular piece of data from the available list, and drop that into the slot they want that data to apply to.

Efficient and intuitive databinding for mobile applications

A system includes download location information in an unprotected Uniform Resource Locator (“URL”), where the download location information identifies a download location for downloading an application provided by a cloud system The system further includes login server information in the unprotected URL, where the login server information identifies a login server that is configured to be logged in before downloading the application from the download location Based on the unprotected URL, the application is configured to be downloaded on a mobile device from the download location and after logging into the login server The application may be developed by accessing a web-based application development server in the cloud system, and after the application is developed, the web-based application development server generates the unprotected URL

Discovery of federated logins

A system that generates a visualization user interface. The system receives a selection of a data source, and receives a selection of a visualization template that includes metadata. The system further receives a selection of data attributes corresponding to the data source. The system parses the visualization template for the metadata, and replaces the metadata with binding between a visualization component and the data source. The system then generates the visualization user interface using the visualization component.

Nitin Shah

Papers

User interface component autowiring