How to Write a Prompt That Builds the App You Want

Say who uses the app, the one thing they do, what it must remember and who sees what. Then ask for one change per message. Three full examples inside.

Firevibe Team13 min read

Write a short paragraph that says who uses the app, the one main thing they do in it, what it must remember, and who can see what. Add the screens or pages you already know you need and, if you care, two or three concrete choices about the look. Leave out the technology, the wish list and the sales pitch. After the first build, ask for one change per message, and name the screen, the element and the result you want.

We make Firevibe, an AI app builder, and this is the advice we give for it. Most of it carries over to any builder you describe an app to.

What should a first prompt for an app include?

A good first prompt answers six questions, in plain sentences.

  • Who uses it. Name the people: a trainer's clients, the staff in your office, customers ordering a cake. If there are two kinds of user, name both.
  • The one main thing they do. This is the action the app exists for: order a cake, log a workout, request a laptop. Describe it as the steps a person takes, in order.
  • What the app must remember. Name the things it stores and their details: an order with a size, a flavor and a pickup date; an item with a serial number and a status.
  • Who can see what. Say who signs in, what each kind of user sees, and what each can change. "Staff see only their own requests; the manager sees all of them" is one sentence, and it spares you a round of fixes later.
  • The screens or pages you already know. If you know you want a menu page or a progress screen, list it. If you do not know yet, leave this out and judge the first build.
  • The look, if you care. Concrete choices beat adjectives: a background color, one accent color, the size of the text, the kind of photos. For a website you can also give Firevibe a screenshot of a site you like, or your logo and colors.

What should you leave out of the first prompt?

Leave out anything that does not change what gets built first.

  • The technology. You do not need to name frameworks, databases or hosting. In Firevibe a website is real React and TypeScript, a mobile app is React Native with Expo, and every project comes with a backend, a database, sign-in and file storage, already connected.
  • The wish list. Features for someday make the first build bigger and harder to check. Keep them in a note and ask for them one at a time once the main action works.
  • Vague style words. "Modern and clean" describes almost every app. Say what you would see instead.
  • The pitch. Market size and competitors do not change a screen. One sentence about the business is enough.
  • Things the builder cannot do. Know the limits before you write, so the prompt does not depend on them. In Firevibe, as of November 2026: sign-in for a website or web app is email and password; the built-in AI for your app's own features works with text only, not images or audio; and outside services connect only through the connectors listed on the connectors page, each with your own account. Google Sheets, Gmail and the Microsoft apps are not among them today.

Which kind of project should you choose first?

In Firevibe you choose the kind of project before you type, and there are three.

  • Website covers websites, web apps, SaaS products, dashboards, internal tools and online shops. You get a live preview while it builds and a share link. See what a Firevibe website includes.
  • Mobile app is a real app for iPhone and Android, built with React Native and Expo. You open it on your own phone by installing Expo Go, Expo's free app, and scanning the QR code in your project. See the mobile app builder.
  • Design gives you a set of mobile app screens with no working app behind them. If you later want the working app, open the design and choose Build it; that makes a new mobile app project and leaves the design as it is.

For the mobile path from first sentence to the app on your phone, see how to build an iOS and Android app with AI.

Three weak and strong prompts, written out

These are examples we wrote for this post, not real projects. Each strong prompt is a paragraph a person could type in a couple of minutes.

Example 1: a website for a bakery

Weak:

Make a website for my bakery.

Strong:

A website for Crumb and Co, a small neighborhood bakery. Pages: a home page with this week's specials, a menu with prices, an about page with our story, and a contact page with our opening hours and a map. Customers can order a celebration cake online: they pick a size and a flavor, choose a pickup date at least three days ahead, and pay with Stripe. I sign in to see every cake order in a list sorted by pickup date. Customers do not need an account. Warm look: cream background, dark brown text, large photos of bread and cakes.

Why the strong one works: it names the pages, the one thing a customer does (order a cake), what the site must store (each order with its size, flavor and date) and who sees the orders. The weak one leaves all four to a guess. In Firevibe, Stripe and Google Maps each run on your own account and key.

Example 2: a mobile app for a trainer's clients

Weak:

A fitness app with workouts.

Strong:

A mobile app for my personal training clients. Each client signs in with email and password and sees this week's plan: one screen per training day, with each exercise and its sets and reps. They tick off each set as they finish it and log their body weight once a week. I sign in as the trainer, see all my clients, write each client's plan for the coming week, and see who missed a session. Clients see only their own plan and history. Screens: sign in, this week, a training day, my progress with a simple weight chart, and for me a client list and a plan editor. White background, one bright green accent, and large text that is easy to read mid-workout.

Why the strong one works: it names two kinds of user and exactly what separates them, lists the screens, and describes the main action (ticking off sets) step by step. Extras such as workout reminders can follow as single messages. In a Firevibe mobile app, push notifications and Sign in with Apple are added on request, and Sign in with Apple works in the installed app, not in the Expo Go preview.

Example 3: an internal tool for equipment loans

Weak:

Build a tool to track our office equipment.

Strong:

An internal tool for our office to track who has which equipment. We have about 60 items: laptops, monitors and cameras. Each item has a name, a serial number, a photo and a status: available, on loan or in repair. Staff sign in with email and password, browse what is available, and request an item for the dates they need it. The office manager approves or declines each request, marks items as returned, and sees overdue items at the top of the home page. Staff see only their own requests. The office manager sees everything. When a request is approved, post a message in our equipment channel in Slack.

Why the strong one works: each item's details, its three statuses and the two roles are spelled out, so the first build can have the right data and the right permissions. The Slack message goes through Firevibe's Slack connector, on your own Slack account. For the whole path from a spreadsheet to a working tool, see how to build an internal tool with AI.

Why send one change per message?

Send one change per message because you can check one change quickly and say exactly what to fix if it missed. A list of eight changes gives you eight things to verify at once. If two of them pull against each other, such as a bigger header and a shorter page, you cannot tell which instruction won.

One change per message also keeps the conversation easy to follow: if something goes wrong, you know which message it came from.

The exception is a group of small tweaks to the same element, such as the color and wording of one button. Keep a running list of everything else outside the chat and send it one item at a time, most important first.

Before the first change, use the main action from start to finish as a real user would: order the cake, tick off the set, request the laptop. That shows you what matters most to fix.

How do you describe a change so it lands?

Name the screen or page, name the element, and say the result you want to see. Leave the method to the builder.

Instead ofWrite
Make it look better.On the home page, make the headline larger and put the Order a cake button right under it.
The form is broken.On the Request screen, when I tap Submit, nothing happens. I expected the request to appear under My requests.
Add charts.On the client list, add a small chart next to each client showing their weight over the last 8 weeks.
Change the colors.Change the green accent to a darker green everywhere it appears. Keep the white background.

Two habits help. Report a problem as what you did, what you saw and what you expected, so the fix has something to aim at. And say what must stay the same when it matters: "keep the layout, change only the wording" protects the parts you like.

In a Firevibe mobile app, the app and its backend change together, and the change is on your phone the next time you open the app.

How does pointing at an element work on a web preview?

In a Firevibe website or web app, you can point at an element on the live preview, such as a headline, a photo or a section, and say what should change. That element changes, and the rest stays as it was.

Pointing settles which thing you mean. You still need to say the result: "make this one line on a phone" is a request you can check, and "fix this" is not.

In a Firevibe Design project you can also select an element and describe the change. In a Firevibe mobile app project you describe the change in chat, so name the screen and the element in words.

When should you start over instead of patching?

Start over when the core of the first build is wrong. Keep patching when the details are wrong. Signs that the core is wrong:

  • You chose the wrong kind of project, for example a website when you wanted an app on your phone. One case needs no restart: if you made a Firevibe design and now want the working app, open the design and choose Build it.
  • The app is for different people, or does a different main thing, than you now want.
  • The data is shaped wrong at the root, for example one order per customer when customers place many.
  • You keep fixing the side effects of earlier fixes.

Before you start over, rewrite your first prompt with what the first build taught you. That rewritten prompt is the most useful thing the first attempt gave you.

Starting over means a new first build, and every build draws on the same Firevibe credits. Projects are also capped by plan: as of November 2026, the Free plan allows 1 project, Starter 2 and Pro 5.

A checklist before you send

For the first prompt:

  1. I chose the right kind of project: Website, Mobile app or Design.
  2. It names each kind of user.
  3. It describes the one main thing they do, as steps.
  4. It lists what the app must remember, with the details of each thing.
  5. It says who can see and change what.
  6. It names the screens or pages I already know I need.
  7. It gives a few concrete choices about the look, or none at all.
  8. It leaves out the technology, the wish list and the pitch.
  9. It asks only for things the builder can do, including its connectors.

For every change after that:

  1. I used the main action from start to finish first.
  2. The message asks for one change and names the screen, the element and the result.

If you would rather start from something that already works, the Firevibe library has examples and templates. Or sign up free, with no credit card, and try your prompt. The free credits are enough to build a first product and make an edit, though a first mobile app build with accounts and a server can use all of them.


Frequently asked questions

How long should a prompt for an AI app builder be? Long enough to say who uses the app, the main thing they do, what it must remember and who can see what. For most apps that fits in one or two short paragraphs. Ideas for later features belong in later messages, one at a time.

Do I need to name a framework or a database in my prompt? No. In Firevibe a website is built in React and TypeScript and a mobile app in React Native with Expo, and every project comes with a backend, a database, sign-in and file storage. Describe what the app does and who uses it instead.

Should I ask for several changes in one message? Usually not. One change per message lets you check the result quickly and say exactly what to fix if it is not right. Small tweaks to the same element, such as one button's color and wording, can go together.

Can I point at the part of the app I want changed? In a Firevibe website or web app, yes: point at an element on the live preview and say what should change. In a Firevibe mobile app you describe the change in chat, so name the screen and the element in words.

When should I start a new project instead of fixing the current one? Start over when the core of the app is wrong: it is for different people, it does a different main thing, or it is the wrong kind of project. When only details are wrong, fixing them one message at a time is usually quicker.

Can I start from an example instead of a blank prompt? Yes. The Firevibe library has examples and templates you can start from instead of a blank page.

Generate any product

Build web apps, mobile apps, SaaS, internal tools, marketplaces and more.

Start for free