PROMPT GUIDE
Base44 is the "describe the business, get the app" builder — auth, database, and hosting are built in. The catch: it wants plain product language, not tech talk. If your prompt sounds like a developer wrote it, Base44 gets confused. Here is how to speak its language, plus a free generator that does it for you.
Generate your prompt — free, no sign-up
No "React components" or "API endpoints." Say what the user can do: "clients can book an appointment and get a confirmation email." Base44 wires the tech itself.
"Members have a name and a streak count." "Invoices have a client, a total, and a status." This one habit is 80% of good Base44 prompting — it turns sentences into tables and forms automatically.
"Users can add and edit their entries" is one workflow. Add the next workflow in the next prompt. Stacked workflows in a single prompt produce stacked half-features.
Avoid component, API, schema, state. If a sentence would not make sense to a non-technical founder, it is the right sentence for Base44.
For integrations just say "send email confirmations" or "take payments" — Base44 picks the provider. Naming Stripe or Twiddle yourself only constrains it.
Add [FEATURE] to my app. What users can do: [plain-language outcome]. Each [OBJECT] has [field], [field], and [field]. Rules: - [Who] can [action]; [who else] can only [action]. - Show a friendly confirmation after saving. - Works on mobile and desktop. Do not change existing pages, navigation, or styling.
Almost always because the data was described vaguely. Describe each business object with its fields in one plain sentence — "Members have a name and a streak count" — and Base44 creates the table and forms reliably.
No. Base44 handles the entire stack itself. Technical words steer it wrong. Describe products, objects, and workflows the way you would to a cofounder over coffee.
Name the capability, not the vendor: "send email confirmations," "accept card payments." The free generator phrases all of this correctly for you.