Publish your first web app

Start with one useful page, connect it to a tested workflow, and preview the app before creating a release. Cloudgate supports both visual page building and code-based applications.

Choose a starting point#

• App Store or App Templates: start with an existing application and review its requirements before installing or customizing it.
• Visual Builder: assemble layouts, forms, tables, and charts for an API-backed tool.
• Code Editor: work with application source when you need custom components, routing, or a development workflow.

Open Web Apps → Web Apps to find and manage your app. For visual sites, enter the builder from the selected app; pages belong to that app.

Build one complete interaction#

For a first app, use a read-only list rather than a multi-step transaction:

1. Prepare a sandbox workflow that returns a predictable list of records.
2. Add a page and a table widget, or a page component in your code project.
3. Configure its input API action and the path to the list in the actual response.
4. Display a small set of fields with clear names.
5. Add loading, empty, and failed-request states.

For example, a response of {"result":{"items":[...]}} needs a table data path of result.items. A successful request with the wrong data path can still produce an empty table.

Add access if the data is private#

Configure the Identity Provider, test a signed-in user, and authorize the workflow on the server. Hiding a page or a button does not restrict direct API calls.

Preview and release#

Test the page at narrow and wide screen sizes. Refresh a direct page URL, sign out and back in, and verify the selected API environment. Use fixture records for anything that writes data.

Create the app release, inspect its build result and preview, and review workflow dependencies before approving publication. An app build and a workflow release are separate changes; both must agree on the request and response contract.

Continue with publishing and rollback.