Quickstart with the builder
No coding agent? The built-in builder writes the app for you from a description in plain words. By the end of this page you will have a working app with real screens, a database and sign-in on a preview link, and you will know where to change it afterwards.
What you need
- An email address, or a Google or GitHub account.
- A rough idea of who will use the app and what each of them needs to do.
Steps
- Create an account at /signup. You land on the dashboard. Plan limits and AI credits are on the pricing page.
- Create a project. Each project is one app with its own database, files and preview, so experiments never touch each other. You can also start from one of the templates.
- Describe the app in the editor chat. Name the people who use it, what they do and what each may see:
A booking app for a yoga studio. Members sign up, see this week's classes and book a mat; they see only their own bookings and can cancel. Instructors manage the timetable and see every roster. A class can't be booked once it's full. Let people sign in with Google. - Watch it build. The builder writes the contract, creates the tables and access rules, compiles the screens and arms the workflows. The preview updates as it goes. You can interrupt and change direction at any time.
- Try it as each user. Use the demo sign-ins the builder lists to sign in as each role and go through the real flows.
- Change it by chatting.Ask for changes in product words ("add a waitlist when a class is full") rather than code words.
- Publish. Click Deploy. Appbricx runs verify, takes a backup and puts the app on
https://<name>.apps.appbricx.com.
Find your way around the editor
| Area | What it is for |
|---|---|
| Chat | Describe changes. Plan mode talks through an approach before anything changes. |
| Preview | The app running against your development database, with real sign-in and data. |
| Files | The generated code. It is yours: export it any time. |
| Backend | Tables, data, SQL, schema, backups, users, logs, live events, secrets, workflows and more. See operating your app. |
| Deploy | Publish, deploy history and your domain. See publishing. |
Gotchas
- The preview is not the live app. It uses the development database. Your users see the published app, with its own production database.
- Hand over to an agent any time. The builder and coding agents edit the same contract. Connect Claude Code later and it carries on where the builder stopped.
- Use your own AI key to keep builder costs down. See AI keys.