
This post is for beginners who have never built an app. I will walk through Emergent from a blank screen to a live link you can send to a friend. We will build a small expense logger because it has a database, a form and a list, which is everything a first app needs and nothing more.
Before you start: three decisions
Emergent asks you three things up front. Make these choices on purpose.
1. App type
On the home screen you pick Full Stack App, Mobile App, Landing Page or Brainstorm. The app type is fixed for that job, so you cannot switch later. For this walkthrough, pick Full Stack App. If you are not sure what you are building yet, start with Brainstorm instead.
2. Agent
Emergent has several build agents. In short: E-1 is the original and wants step-by-step direction, E-2 aims for speed and reliability on complex integrations, and E-3 brainstorms, writes a plan and then builds mostly on its own. If you are unsure, open Emmy (the assistant in the bottom-right corner) and ask which agent fits your idea. Emmy does not write code, but it is good at scoping and can draft your first prompt.
3. Build or Plan
The chat box has a Build/Plan switch. In Build mode the agent starts coding as soon as you send. In Plan mode it shows you a proposal card and builds nothing until you click "Looks good, let's build it." I tell every beginner to use Plan for a first build. One catch: Emergent's docs say Plan mode is not available in Brainstorm or E-3 sessions. If you pick E-3, it runs its own brainstorm and plan step instead.
Step 1: write a first prompt that fits on one screen
Emergent's docs suggest a first prompt covers what the app is, who uses it, and the main things people do. You do not need to name a tech stack. The agent picks it (for web apps that is a React front end, a FastAPI back end and MongoDB).
Here is the prompt I would use:
Build an expense logger for my personal use. No login for now.
I can:
1. Add an expense with amount, category (Food, Travel, Bills, Other) and date
2. Filter the list by category
3. See the total for the current month at the top
Design: clean and simple, dark mode, the add form sits at the top of the list.
How it should feel: fast. Adding an expense should take under 10 seconds.
Notice what is missing: user accounts, charts, exports, budgets. Those come later, one at a time. A small first build is cheaper, faster and easier to test.
Step 2: answer the agent's questions
During planning, the agent may ask clarifying questions, such as whether users need to log in or whether to load sample data. Answer them plainly. Say yes to sample data, because it makes testing the preview much easier.
If you are in Plan mode, read the plan card. Check three things:
- Are the pages what you expected?
- Is it storing the fields you listed, and nothing strange?
- Did it add features you did not ask for?
If anything is off, click Request changes and say so. Changing a plan costs far fewer credits than changing built code.
Step 3: watch the build, then read the summary
Once building starts, you will see the agent work through planning, scaffolding, writing code and testing. You do not approve each step. When the round is done, it posts a summary in the chat and a live preview appears.
The preview is private. Only you can see it, and it goes to sleep after a while if you leave it alone. That is normal.
Keep an eye on your credit balance in the top-right corner. If you want a hard stop, Emergent lets you set a per-session budget when you start a task, and the agent pauses if it hits it.
Step 4: test it like a stranger would
Do not trust "it works" from anyone, including the agent. Emergent's own docs say that when the agent says it verified something, it checked the preview only. So click through it yourself:
- Add three expenses in different categories.
- Try to submit the form empty. You should get a clear error, not a blank row.
- Type letters into the amount field.
- Filter by each category and check the monthly total.
- Open the preview on your phone, or use the mobile view, and add one more.
You can also ask the agent to test for you. This prompt is straight from the spirit of Emergent's testing guide:
Test the app end to end and report anything broken.
Do not fix anything yet. Just give me a numbered list of problems.
Asking for a list first means you choose what to fix, instead of paying for fixes you did not need.
Step 5: fix one thing at a time
When you report a bug, say what you did, what you expected and what happened. Paste the full error from the browser console if there is one. For visual issues, drag a screenshot into the chat.
When I add an expense with a date in the past, the monthly total does not change.
Expected: the total only counts expenses dated in the current month.
What happened: the total includes every expense ever added.
Please fix only the monthly total. Do not change the layout.
If a change goes badly, you do not have to argue with the agent. Emergent saves a checkpoint after every agent turn. Use the Rollback button on an earlier message to return to a working state.
For small visual tweaks, try Canvas edit: in the preview pane, click Edit, select an element, and describe the change.
Step 6: publish to a live link
When you are happy with the preview:
- Click Publish in the top toolbar.
- Run the Health Check, which scans for problems that would break the live app.
- Start the deployment. The first one takes roughly 10 to 15 minutes.
- Copy the production URL and open it in a private browser window.
Three things to know about going live:
- Hosting costs credits every month. A live app costs a monthly fee per app, starting at 50 credits. If you shut the app down, that charge stops. Your code and database stay.
- Preview and live are separate. New changes only reach the live app when you click Re-publish. Production also starts with its own fresh database, so your sample data will not be there.
- Secrets do not carry over automatically. If you add API keys later, you set the live values separately. My integrations post covers this.
If you want your own domain, the Domain settings let you link one by adding an A record at your DNS provider. SSL is set up for you once the domain verifies. This works for web apps, not mobile apps. Emergent's getting started docs walk through each screen if you get stuck.
Step 7: test the live app, not just the preview
Run the same five checks from Step 4 on the live URL. Most "it worked in preview" problems show up here, usually because of a setting or key that differs between the two. Catching them before you share the link saves you an awkward message later.
What to add next
Once the basic app works live, pick one next feature. Not three. Good candidates for this app are a login so it can hold more than one person's data, a monthly chart, or a CSV export. Add one, test it, re-publish, and repeat.
Where to go next
If this was your first build, the free Intro to Vibe Coding course at /courses covers the testing and scoping habits that keep small apps from turning into messes. For more first-app ideas with ready-made specs, browse /recipes.
What would have made it better?