​
Core principles for great prompts

These four principles will help you write prompts that produce stronger, more useful results.
1

Be clear and specific

Base44 is built to read between the lines, but a little context goes a long way. Start with who the app is for, what it should do, and any must-have features. You don’t need to write like a developer, just be clear about what you care about.
Here’s a good example: “I want an app that helps personal trainers manage client workout plans and track weekly progress.”
The AI works best when you give it a simple foundation to build on. Keep it in plain English, and don’t worry about being perfect. The goal is to give the AI enough to run with
2

Focus on the user’s journey

Consider how a user will interact with your app. If you have a clear vision about the sequence of actions a user will take, it will help Base44 build the right structure.
Example: “Users sign up, create a new project, set milestones, and track their progress daily.”
3

Describe the “what,” not the “how”

We handle all of the complexity behind the scenes so there’s no need to describe how the back end should function. Just describe what the app should do or look like.
Try this as an example: “The app should store user data, load quickly, and feel clean and modern.”
4

Iterate and refine

Remember, while Base44 will give you a fully-functional output, your first prompt is still a starting point. You can always work with it on big changes, small refinements, or entirely new directions.

​
Prompt frameworks

Not sure how to articulate what you want to say? Use these frameworks below for inspiration.
  1. The “Who / What / Why” Prompt Perfect for when you’re starting from scratch.
    • WHO is this app for?
    • WHAT does it help them do?
    • WHY would someone use it?
      Example:
      WHO: This app is for independent consultants.
      WHAT: It helps them manage client projects, contracts, and deadlines in one dashboard.
      WHY: To save time, stay organized, and never miss deliverables.
  2. The “User Story” Prompt A variation on the “who/what/why” prompt through a different lens.
    Examples:
    “As a freelance designer, I want to send branded invoices to clients and track when they’re paid, so I can stay on top of my cash flow.”

    “As a new parent, I want to log my baby’s feedings and naps, so I can spot patterns and share them with my pediatrician.”
  3. The “Feature Breakdown” Prompt When you’re mid-build and come up with a great addition to your app.
    Example: “I want to add the following capabilities:
    • Add and organize leads
    • Track outreach status (new, contacted, interested, closed)
    • Add notes and follow-up reminders”

​
Techniques to get better results

When you’re refining your app, there are some ways you can talk to Base44 that will help it execute on your vision. Here they are, along with some pro tips to take them to the next level.
TechniqueWhen to Use ItExamplesPro Tip
“Make it more…” / “Make it less…”Adjust tone, layout, or emphasis- “Make the header less bold.”
- “Make the CTA more persuasive.”		Add why: “Make the CTA more persuasive because it’s the final step in the user’s journey.”
“Add a…” / “Remove the…”Add/remove specific features or UI blocks- “Add a comments section to each task.”
- “Remove the pricing page for now.”		Group actions for greater efficiency: “Add a comments section and move it below the task list.”
“Change [this] to [that]”Adjust text, visuals, layout, or component logic- “Change the sidebar color to charcoal.”
- “Change the ‘Submit’ button to say ‘Send Request’.”		Layer context: “Change the button text to match the friendly tone used in the rest of the app.”
“It should feel like…”Borrow familiar app styles to guide layout or behavior- “It should feel like a mix between Duolingo and Habitica.”
- “Like a lighter version of Airtable.”		Clarify which parts: “Use Duolingo’s playful tone and Habitica’s gamified progress system.”
“Add logic for…”(optional)Add functional rules or flows without needing code- “Add logic to hide completed items from the default view.”
- “Send a reminder if no action in 3 days.”		Describe the desired outcome once the logic is added: “Add logic so users get nudged if they haven’t logged in for a week.”
“Group or organize…”Structure content for clarity or workflow- “Group tasks by category”
- “Organize settings into collapsible sections”		Mention user needs: “Organize tasks by category so users can quickly find what they need.”
“Add conditional behavior…”Introduce smart branching or state-based functionality- “Only show the download button after payment is confirmed.”Start simple, expand later: “Add the condition first, then I’ll add variations per user type.”
“Let users…” statementsFrame functionality from the end-user’s perspective- “Let users upload documents and tag them.”
- “Let users bookmark resources for later.”		Frame the functionality around unlocking value for the user: “Let users upload documents and tag them so they can easily find them later.”

​
Build in layers when building complexity

If your app is getting more complex, break your requests into layers:
  1. Start simple: “I want an app for tracking daily habits with streaks and reminders.”
  2. Stack on features: “Now add the ability to group habits by theme (e.g., health, productivity).”
  3. Polish the visuals: “Make the habit cards more colorful and use emoji icons for each.”
Prompting this way lets you build incrementally, without overwhelming the system or yourself.

​
Quick recap

  • Don’t overthink your first prompt. You can always adjust.
  • Give context, not just features. Why does this app matter?
  • Reference tools you like. If you love how another app feels, say so.
  • Talk like you’d explain to a colleague. Plain language > technical terms.

​
Troubleshooting tips

​
You’ve got this

You already have the ideas. Now you’ve got the words to bring them to life. You don’t need to be technical to build something powerful. Start simple, speak naturally, and don’t be afraid to iterate.