Skip to main content
A prompt is simply a description of what you want, written in your own words. There is no code, no syntax, and no special commands to learn. You describe your app, and Base44 builds it. Because your whole app is built from what you type, your words are your building material. The clearer the picture you paint, the closer the result will be to what you had in mind. This guide walks you through painting that picture, from your very first prompt to the small refinements that make an app feel finished.

​
How building with prompts works

Building in Base44 is a loop, not a single instruction you have to get right on the first try. You describe, Base44 builds, and you shape the result together over a few rounds. Each round looks like this:
  • Describe: You say what you want in plain language.
  • Build: Base44 creates or updates your app in seconds.
  • Review: You look at what changed and decide what comes next.
  • Refine: You give feedback, and the app updates again.
Treat your first result as a rough draft you can mold, not a final answer. That mindset takes the pressure off, and it is how the best apps come together.

​
Writing your first prompt

Your first prompt is the foundation for everything that follows, so aim to describe the heart of your app rather than every detail. You can always add more later. Focus on what the app is, who it is for, and the main things people should be able to do. A quick way to shape this is to think through the who, what, and why of your app:
  • Who: Who will use it, such as freelancers, students, or your whole team.
  • What: What it helps them do, such as track expenses or book appointments.
  • Why: Why it is useful to them, such as saving time or keeping everything in one place.
Here is that thinking turned into a prompt: 
Build an expense tracker for freelancers who bill several clients at once.
People can log an expense, tag it to a client and a category, and see a
monthly total for each client. The goal is to make tax season painless.
Not sure where to start? Turn on Plan mode before your first build. Toggle Plan in the prompt box and Base44 asks you a few questions about your app, then turns your answers into a structured plan you can adjust before anything is built. It costs only a fraction of a credit per message. Learn more about plan mode

Ready to get started?

Take me to Base44 to build my app

​
Describing your app clearly

The gap between a rough result and a great one usually comes down to how much of the picture you share. These 5 moves help Base44 build the app you actually pictured, whether it is your first prompt or your fiftieth.

​
Paint the screen, not just the idea

Base44 fills in anything you leave out with its best guess, so describe what you want to see on the page. The more concrete you are, the less it has to invent.
  • Vague: “Make a dashboard for my sales.”
  • Clear: “Make a sales dashboard with 3 cards along the top for total revenue, deals won, and deals lost, then a bar chart below showing revenue by month.”

​
Say why you want it

When you explain the reason behind a request, Base44 can make smarter choices about the details you did not spell out. The why is often more useful than the what.
  • Just the what: “Put the sign-up button at the top.”
  • With the why: “Put the sign-up button at the top so it is the first thing a new visitor sees.”

​
Borrow from apps you already like

You do not have to describe a look from nothing. Naming an app people know is a fast shortcut to the feel you want, as long as you say which part you mean.
  • “Organize it like Trello, with cards I can drag between columns.”
  • “Make it feel as calm and uncluttered as Notion, but keep my own brand colors.”

​
Build one piece at a time

Packing an entire app into a single prompt makes the result harder to get right and harder to fix when something is off. Start with the core, get it working, then layer features on one by one. 
Start:  Build a booking app where clients pick a service and an open time slot.
Next:   Now email the client a confirmation as soon as they book.
Next:   Now hide time slots that are already taken so nothing gets double-booked.
Focused prompts also tend to be gentler on your credits, because a small, clear change is less work behind the scenes than a broad one that touches many pages. Dragging elements or editing text yourself with Visual Edits does not use credits at all. Learn more about credits

​
Ask for the fix, not the flaw

When something looks off, describe where you want to end up rather than only what is wrong. Base44 builds from your target, not from your frustration.
  • The flaw: “The homepage looks cluttered and cramped.”
  • The fix: “Give the homepage more room to breathe: fewer items per row and more space between the sections.”

​
A recipe for look and feel

When the design matters to you, describe 3 things together: what the app does, how it is laid out, and the mood it should have. Combining them gives Base44 a full picture in a single prompt.

​
Function

Tell Base44 the job your app is doing, because an online store and a personal portfolio should not look the same. A store needs clear product grids and a fast path to checkout, while a portfolio needs personality and a strong first impression.

​
Layout

Tell Base44 how to arrange things on the screen so it does not have to guess. For example:
  • Grid of cards: Content sits in tidy boxes, which suits dashboards and feature-heavy apps.
  • One long scroll: The app is a single page where sections appear as you scroll, which suits stories and landing pages.
  • Split screen: The screen is divided in 2, often with text on one side and a visual on the other.

​
Visual style

Tell Base44 the mood you want, and go further than “clean” or “modern.” For example:
  • Calm and professional: Soft colors, plenty of white space, and simple type.
  • Bold and playful: Bright colors, rounded shapes, and friendly icons.
  • Sleek and premium: A dark background, high contrast, and elegant fonts.

​
Refining your app as you go

Once your app exists, most of your time goes into refining it through the AI chat. The phrases below are reliable ways to ask for a change, each with a tip to sharpen the result.
TechniqueWhen to use itExamplePro tip
”Make it more…” or “Make it less…”Adjusting tone, layout, or emphasis”Make the header less bold.”Add the reason: “Make the call to action more prominent because it is the last step people take."
"Add a…” or “Remove the…”Adding or removing a feature or section”Add a comments section to each task.”Group related changes: “Add a comments section and place it below the task list."
"Change [this] to [that]“Editing text, colors, or components”Change the Submit button to say Send request.”Layer in context: “Change the button text to match the friendly tone used across the app."
"It should feel like…”Borrowing a familiar app’s style”It should feel like a mix of Duolingo and Airtable.”Say which parts: “Use Duolingo’s playful tone and Airtable’s table layout."
"Add logic for…”Adding a rule or flow without code”Hide completed items from the default view.”Describe the outcome: “Remind people if they have not logged in for a week."
"Group or organize…”Structuring content for clarity”Group tasks by category.”Mention the reason: “Group tasks by category so people find what they need quickly."
"Only show… when…”Adding behavior that depends on a condition”Only show the download button after payment is confirmed.”Start simple, then expand: “Add this condition first, then I will add variations per user type."
"Let people…”Framing a feature from the user’s point of view”Let people bookmark resources for later.”Add the value: “Let people tag their documents so they can find them again easily.”

​
Getting more from Base44’s tools

The chat box is not your only way to communicate. These tools let you point, plan, and protect your work, and they often reach the result faster than words alone.
  • Point instead of describe: With Visual Edits, click straight on the element you mean and describe the change right there. It is the clearest way to say “this one, not that one.” Learn more about the AI chat
  • Plan before you build: Use Discuss mode to talk an idea through with the AI before it changes anything, so you can agree on a plan without touching your live app or spending credits on changes. Learn more about the chat modes
  • Show, do not just tell: If you have a design in mind, import it from Figma so Base44 can match something real instead of a description.
  • Set your rules once: Use AI controls to add instructions the AI should remember on every prompt, and to limit changes to only the areas you want touched. Learn more about AI controls
  • Experiment without fear: Restore any earlier version of your app at any time, so you can try bold ideas knowing you can always go back. Learn more about reverting changes

Need a starting point?

Browse the Prompt library for ready-made prompts you can copy, remix, and build on.

​
Common mistakes to avoid

A few habits trip people up early on. Keeping these in mind will save you time and lead to better results.
  • Being too vague: Requests like “make it better” or “fix it” give Base44 nothing to work with. Say what you want changed and how.
  • Asking for everything at once: Cramming payments, reviews, analytics, and inventory into one prompt invites confusion. Build the core first, then add features step by step.
  • Assuming the AI remembers other chats: If you are picking up an idea from a different conversation or a while back, briefly remind Base44 of the context.
  • Expecting it to read your mind: If you have a specific layout or flow in your head, describe it as clearly as you can rather than hoping Base44 lands on it.

​
FAQs

Here are answers to common questions about writing prompts and working with the AI chat.
It can take a few attempts to land on the right result, especially when a request is open to interpretation. To get closer faster:
  • Use Visual Edits to click the exact element you want to change and describe the change there.
  • Explain what you want to happen, rather than what looks wrong.
  • If a prompt is not working after a couple of tries, rephrase it and use words like redesign or rebuild.
  • Keep your language simple and natural. The clearer the request, the more accurate the result.
Use AI controls to limit the AI’s changes to only the areas you want updated. This is especially helpful when other parts of your app keep getting altered unintentionally. Learn more about AI controls
Use Discuss mode at the bottom of the AI chat. It lets you talk through ideas, review logic, and plan steps with the AI before any changes are made or credits are used. Learn more about the chat modes
If the AI is taking too long or seems stuck, try refreshing the page or resending your prompt. This usually gets things moving again.
Some features might not be supported yet. If you are unsure whether something is possible, ask in our Discord help channel.