Manage Client Applications

The App Development page is used to browse, customize, save, preview, and publish applications. Applications are hosted on the platform, so when users publish them, they are available to other users.

Note: A number of third-party common libraries are available for use under app_cdn.

You can do the following:

  • Upload an application. In the New Upload tab, you can upload the ZIP file of your application. The uploaded application is shown in the All Uploads tab.

  • Edit application files (Browse): Access the application files in a file editor and make the changes. You can then save, test, and publish the application to view the changes. Every time you edit an application and save it a new version of the application is saved. You can view the latest version number of the application in the Current Version column. When you are publishing an application, you can use these versions. Multiple users can access applications, but cannot merge changes concurrently.

  • Clone an application (Clone). After cloning an application, update the app.desc.json file.

  • Delete an application (Delete).

  • Download an application (Download). You can work offline and reupload them.

  • View application details like owner, created time, versions (Details). Here, you can select a previous version of the application to view it.

  • Publish an application (Publish).

  • Launch an application (Launch): You can launch either the latest application or a previously published version of the application.

  • The following properties can be passed to an application from the appName.app.desc.json file:

    Caution: For the properties marked as mandatory, you can modify their value, but do not unset the property, otherwise the application might not function properly.
    • appImage (mandatory for applications targeted for the mobile devices. Not applicable to the desktop applications.) - The path to the image depicting the application.

    • category (optional) - A category used to group your applications.

    • configPage (mandatory) - The path to the configuration file for the application.

    • defaultLocale (optional) - The locale in which the application is displayed.

    • description (mandatory property for applications targeted for mobile devices.) Short description for the application.

    • errorPage (optional) - The path to the error page for the application.

    • indexPage (mandatory) - The path toindex.html file for the application or the landing page for the application.

    • library (optional: default=false) - Boolean flag that describes if the application is a library that can be used by other applications.

    • loginPage (mandatory) - Application is directed to this page when the user logs in.

      Note: The out-of-the-box example application in Application Development uses the login component provided by the framework: /apps/logincomponent/login.html. Therefore, you have the option of using that same login component, or redirect to a custom login page using this property.
    • mobile (optional: default=false) - Boolean flag that describes if the application is for mobile devices.

    • support (optional) - Languages supported by mobile applications.

      Caution: Removing any of the mandatory properties might prevent the application from operating correctly.