Build your first working app with AI. No coding experience required.

Know what the main words mean

You do not need to learn programming to follow this guide. You only need an Adios account, a modern web browser, and enough time to read the AI agent's plan and test what it creates.

Template

A working starter app. It gives the AI a safe foundation instead of an empty project.

Workspace

The online home for your source files, AI conversation, preview, logs, and deployment controls.

Preview

A test version you can open before changing the public app.

Build

A production check that prepares the app and catches many problems before release.

Deploy

Publish a reviewed version so other people can reach it on the web.

Health check

A small automatic test Adios uses to confirm the app is responding.

Describe one person, one problem, and one useful action

A first app becomes much easier when it has one clear job. This guide uses a renovation price estimator: a visitor selects three options and receives a rough price range. It is interactive and useful, but it does not need private data or another service.

I want to build [APP NAME] for [WHO IT HELPS].
The main thing a visitor should be able to do is [ONE ACTION].
It should feel [THREE STYLE WORDS].
For the first version, do not add [FEATURES TO LEAVE FOR LATER].

Create your Adios app from the Next.js template

The template already contains the framework, start command, deployment file, and health check. Your first deployment confirms that foundation works before the AI changes it.

1. 1Open the Next.js template and sign in or create your Adios account.
2. 2Review the selected template, region, resources, and deployment settings shown by Adios.
3. 3Create the app and follow the deployment log until the starter is healthy.
4. 4Open the generated HTTPS address. Copy it somewhere safe; you will paste it into the AI prompt.
5. 5Open the app's workspace. This is where you will chat with the AI agent and preview the result.

Paste one complete request into the workspace

Open the AI conversation inside your workspace. Replace the bracketed URL below with the HTTPS address from the starter deployment, then paste the entire request. Asking for a plan first gives you a chance to correct a misunderstanding before any source files change.

I am new to building apps. Help me turn this starter into a complete first version of an app.

The app:
- Name: BrightBuild Project Estimator
- Audience: homeowners planning a small renovation
- Main job: let someone choose a project type, room size, and finish level, then show a rough price range
- Style: calm, trustworthy, modern, and easy to read

What to build:
- A clear home page that explains the estimator
- A working estimator with project type, room size, and finish level inputs
- An instant estimated price range calculated in the browser
- A short “How it works” section, an FAQ, and a contact button
- A clear note that the estimate is a guide, not a binding quote
- A responsive layout that works on phones and computers
- Accurate page title and description, plus robots.txt and sitemap.xml for this URL: [PASTE YOUR ADIOS APP URL]

Rules:
- Keep the current Next.js project and its Adios deployment setup.
- Do not remove adios.yaml, package.json, or the existing health route.
- Do not add login, payments, a database, external APIs, or paid services.
- Do not collect or store personal information.
- Do not invent reviews, customer counts, awards, or business claims.
- Use clear placeholder contact details and tell me where they appear.
- Before editing, give me a short plan in plain English.
- After I approve the plan, build the app, run the existing lint and build checks, and explain what changed without jargon.

Open Preview and use the app like a visitor

Wait for the agent to finish its changes and report the lint and build results. Then use the workspace Preview control. A successful build is important, but it cannot tell you whether the words make sense or the estimator feels useful.

• ✓The page opens without an error or blank screen.
• ✓Changing project type, size, or finish changes the estimate.
• ✓The estimate is clearly described as a rough guide.
• ✓Every button and link goes somewhere useful.
• ✓The text is comfortable to read on a phone and a computer.
• ✓There are no fake reviews, unexplained claims, or forgotten placeholder words.
• ✓Refreshing the page still loads the app correctly.

You do not need to understand every changed file. In the workspace review, confirm that the agent changed the page and styles while keeping adios.yaml, package.json, and the health route in place.

Give specific feedback, one short round at a time

“Make it better” leaves too much room for interpretation. Say what you saw, what you expected, and where it happened. Test the new preview after each round so a small visual request does not break the main action.

Please fix only these items in the current app:
1. [DESCRIBE THE FIRST PROBLEM]
2. [DESCRIBE THE SECOND PROBLEM, OR DELETE THIS LINE]

Keep everything else as it is. Do not remove the Adios deployment files or health route. Run the existing checks after the change, then tell me exactly what I should test in Preview.

Run one final review, then deploy

Paste this final request after the preview looks right. It turns your visual review into a release checklist and tells the agent not to publish on its own.

Please perform a final release review of this app.

Check that:
- the main estimator works with several input combinations;
- the layout is readable on a phone and a computer;
- every link and button has a clear result;
- there is no unfinished placeholder text except the contact details we discussed;
- the page title and description match the app;
- robots.txt and sitemap.xml use [PASTE YOUR ADIOS APP URL];
- the health route still works;
- no passwords, tokens, or private information appear in the files;
- the existing lint and build checks pass.

Fix only problems you find. Then give me a plain-language release checklist. Do not deploy until I approve it.

1. 1. Read the result. Make sure the lint and build checks passed. If either failed, ask the agent to fix the failure and rerun it.
2. 2. Open Preview again. Test the estimator once more after the final fixes.
3. 3. Use the workspace deploy controls. Review the version being released, start the deployment, and follow its build log.
4. 4. Wait for healthy. Do not close the page at the first success message. Confirm the new release becomes healthy and is serving the public route.

If the log fails, copy the final error—not the entire log—into the AI conversation and ask for a plain-language explanation before approving another change.

Check the public app, not only the deployment message

Open the HTTPS address in a new browser tab. Test it as though you have never seen the project. A release is finished only when the public app responds and its main feature works.

Create a source checkpoint before adding more features

A Git commit is a named checkpoint for your source. In the workspace, review the changed-file list and create a commit such as Build first BrightBuild estimator. Connect and push to a remote Git repository when you want another copy outside the workspace.

Add complexity in this order

1. Next 1

   Improve the public page

   Refine the words, colors, layout, and estimator choices.

2. Next 2

   Connect a custom domain

   Give the live app an address that belongs to you.

3. Next 3

   Add saved data

   Introduce a database only when the app truly needs to remember something.

4. Next 4

   Add private services

   Store credentials in Adios Secrets, never in the AI prompt or source.

Get unstuck without guessing