Skip to guide
Brandlit
FIELD NOTE / 01 · 4 min

From idea to working app

Write a brief, build with your agent, and refine the result.

Inside this guide
01 / 01

Start with the work it should do

Open App Studio and describe who the app is for, what they need to do, and what should stay saved. A concrete example helps: “A project tracker for a designer. Add projects, change their status, filter the list, and keep changes across visits.”

Use Build guide inside the studio to explore supported examples and limits. Choosing an example fills the brief; it does not begin a build.

01 / 02

Build with your Brandlit agent

Sign in to keep your projects together, then choose Build app. The hosted agent checks the brief before generation. If a requested service is unavailable, edit the brief before continuing; an existing app is kept intact.

App building runs through Brandlit’s hosted API. No personal API key or desktop helper is required. Your account’s plan and usage limits apply.

01 / 03

See it, use it, refine it

Try the result in Preview. Switch between desktop and phone sizes, use the app’s real controls, and ask the agent for a specific change. On a phone, Agent and Workspace switch between the conversation and your app.

Code opens the source files. After an edit, Save & check creates a checked version. New typing remains yours while a save finishes. Unfinished briefs and code are backed up privately to your account; a recovery notice lets you choose between competing copies.

01 / 04

Publish when it is ready

Use Keep it working to protect a workflow that matters to you, then publish a passing version. Publishing gives the app a hosted address. Make private removes public access again.

Shared team apps use one document; private client apps give each invited account its own document. Review People & data before sharing its address. A published app still needs your judgment about whether it does the job well.