Apps
Build and publish software for the way your team works.
An app is software you build with Continual: a dashboard, customer portal, internal tool, or public website. It gives people a dedicated interface for work they need to do repeatedly. Its source lives in your project repository.
Build an app
Start a thread and tell the agent who the app is for, what they need to accomplish, and which data or services it should use. Describe the workflow and the decisions people should be able to make.
For example: “Build an invoice dashboard for account managers. Show overdue invoices by customer, let each manager prepare a reminder, and keep a record of follow-up.”
The agent can create and edit the app source, run checks, and prepare a preview. Keep related apps in the same project when they should share source, connections, and data.
Preview and refine
Use the preview in the thread to try the app as its intended user. Check the main workflow, review the content, and ask the agent for changes. Explain what should happen when input is missing or a service is unavailable, as well as when everything goes well.
A development preview depends on the development server serving it. Publish a built version when you want the app to run independently of that server.
Use data and connections
Database-backed apps on the same branch share its managed PostgreSQL database. The app source defines its tables and data behavior. Apps can also call project and connection tools through the Continual SDK, with tool access configured for the published app.
Use connections for external services and automations for recurring work. Tell the agent which account and records the app should use, and what access its users should have.
Publish and share
Ask the agent to publish the app when it is ready. A published app has a stable URL. Choose whether it should be public or private before sharing it; private apps require sign-in. Visibility controls access to the app, while its backend must enforce access to individual records and actions.
Each app belongs to a branch and has its own versions and deployments. Check the branch and data before publishing an update. Developers can also publish from the CLI.
Keep improving
Return to a thread to fix a problem, change the design, or add a capability. Describe the current behavior and the result you want, review the preview, and publish the update when it is ready.
See Publishing for deployment targets, app access, history, and unpublishing.