Build your first app

Start in Studio with one task people should be able to complete. A small scope gives you a useful way to judge the first version. On Free, our build agent is free for your first app.

1. Describe the experience

Create a task tracker with a title, due date, and status for each task. Show open tasks first. Let me add a task, mark it complete, and filter by status. Save the records so they are still there when I return.

Use invented example data initially. Explain whether this is a personal tool, a shared team space, or an app where each person should see only their own tasks.

2. Try the first version

Add two tasks. Change one, refresh, and check that the saved state is correct. Try an empty title and a past date. If there is sign-in, use a second account to check the intended access boundaries.

3. Refine one behavior at a time

Ask for a precise change, such as “Keep completed tasks visible in their own filter.” Repeat the same task after the edit and confirm that existing records still behave as expected.

4. Publish and use it

Review the app’s configuration and account usage in Studio, then publish when the essential flow works. Open the published link separately and repeat the task. Keep a short list of improvements based on actual use.

A task tracker saves records, so it is an app with data, not a one-page site.

Plan: Build and preview it on any plan. Putting it live needs Go or Pro. See pricing.

Later, a language model could help turn a note into proposed tasks. Review those suggestions before saving them. It is a separate addition to the task tracker, with its own context and usage requirements.

Publishing · Data · Plans