Skip to main content
Every app on Base44 starts as a sentence somebody typed. This library is a collection of sentences that work, written out in full so you can copy one, change the parts in brackets, and send it. These are not only ideas for what to build. They cover the whole life of an app: starting it, adding logins and uploads, making it look like you meant it, putting it to work while you sleep, and fixing the parts that came out wrong. Use one as-is, or read a few and start writing your own.
How to use this page:
  • Fill in the brackets: Anything in [square brackets] is a placeholder. Swap in your own words before you send the prompt.
  • Send one at a time: Most prompts here are a single step. Send one, look at what changed, then send the next.
  • Change anything you like: These are starting points, not spells. A prompt that describes your idea in your own words always beats a perfect one that describes somebody else’s.

Start here

If you’re staring at an empty prompt box, start with whichever of these 5 sounds closest to what you have in mind. Each one is a complete first prompt that builds a working app. Turn a spreadsheet into an app
Why this works: Starting from something you already keep by hand gives Base44 real columns and real records to build around, instead of a blank guess. Build the app you keep wishing existed
Why this works: Who it’s for, what they do, and why it matters. Those 3 details let Base44 make sensible decisions about everything you didn’t mention. Collect answers from other people
Why this works: It describes both sides of the app, what visitors see and what you see, so Base44 sets up access and notifications correctly the first time. Make something private, just for you
Why this works: Saying it’s private up front tells Base44 to lock the app down from the start, so you don’t have to retrofit access rules later. Start from a look you like
Why this works: Naming a site people know, plus the exact sections in order, gives Base44 a layout to follow instead of a mood to interpret.

Not sure what you want yet?

Turn on plan mode before your first build. Base44 asks you a few questions, then turns your answers into a structured plan you can adjust before anything gets built.

Starting a business or work app

These prompts build tools for running something: a business, a team, a side hustle. Each one gives you a working app you can put real data into on day one. Invoice tracker
Stock tracker with reorder alerts
Why this works: The sorting rule and the highlight tell Base44 what the page is for. Without them you get a table that’s accurate and useless. Internal request tracker
Time tracker

Starting a client-facing app

These prompts build things other people use, where the experience they get matters as much as the data you collect. Client portal
Booking page
Why this works: Spelling out the rule, that a booked slot disappears, is what prevents double bookings. Describe the rule, not just the feature. Proposal generator
Event RSVP page

Starting a knowledge or content app

These prompts organize information so it can be found again, which is most of what internal tools actually do. Team knowledge base
Content calendar
Course companion

Starting a personal app

These prompts are for your own life. They’re small enough to finish in an evening and useful enough that you’ll keep opening them. Meal planner
Habit tracker
Trip planner
Gift list

Starting something just for fun

These are the ones people build at 11pm and then send to everybody they know. They’re also the fastest way to get a feel for how prompting works, because nothing is at stake. Absurd name generator
Fake conspiracy generator
Beige flag analyzer

Adding what every real app needs

Once your app exists, these are the features it turns out to need. Send them one at a time to an app that’s already running. Add logins
Why this works: The last line settles what happens to the records that existed before you added logins, which is the part people forget and then have to untangle later. Add roles and invites
Read more about managing access to your app. Add file uploads
Read an uploaded document with AI
Why this works: Asking for a review step before saving keeps you in control of whatever the AI misread, which matters more the more your app leans on it. Add search and filters
Add a dashboard
Add notifications
Why this works: Describing the moment somebody should be told, rather than the bell icon you pictured, lets Base44 wire the notification to the right change in your data. Make it work on a phone
Read more about the mobile experience. Fix the blank screens
Why this works: Blank screens are the most common reason a brand new app feels broken. Asking for them once fixes every page at the same time.

Changing how your app looks

Design prompts work best when you describe the mood, the layout, and what you want left alone. These 4 cover most of what people ask for. Restyle the whole app
Why this works: “Keep the layout exactly as it is” is the guardrail. Without it, a restyle can quietly rearrange your pages while it recolors them. Borrow a look you already like
Unclutter a page
Add dark mode
Read more about design foundations and layout.

Making your app do the work for you

This is where an app stops being a place you type things and starts being something that runs on its own. These prompts set up workflows, emails, AI agents, and connections to the tools you already use.
Workflows are available on the Builder plan and above. If you’re on the Free plan, upgrade to a Builder plan or higher to create and run them.
Welcome and follow up
Email yourself a daily summary
Alert only when it matters
Why this works: Saying what should not happen matters as much as saying what should. It’s the difference between a useful alert and a daily flood you learn to ignore. Add an AI assistant inside your app
Read more about building AI agents. Connect a tool you already use
Read more about connectors. Put AI inside a feature

Getting your app in front of people

Building it is half of it. These prompts cover the part where other people arrive, understand what they’re looking at, and pay you. Charge for access
Read more about setting up payments. Add a landing page
Help people find it in search
Read more about SEO and search visibility. Collect feedback from real people

Fixing and refining

Most of building is not the first prompt, it’s the twentieth. These are the prompts for when something came out wrong, and they’re the ones worth learning by heart. Keep changes where you want them
Why this works: Naming what’s off limits is more reliable than naming only what to change. To make the rule permanent, set it once in AI controls. Report something broken
Why this works: Give the actual behavior, the behavior you expected, and where it happens. Asking what was wrong also teaches you a little about your own app. Ask for less than you got
Why this works: It names the state you want to return to, so Base44 doesn’t have to guess which parts of the last change you liked. You can also revert to any earlier version instead. Make it stop looking generic
Speed up a slow page
Check it’s safe for real people
Why this works: Asking for a review instead of a fix gets you a list you can decide on, rather than a set of changes you didn’t expect. For a deeper check, run a security scan.

Prompt pathways

The best apps grow one prompt at a time. A pathway is a sequence where each prompt adds one thing, so every change is small enough to check before you move on. Here are 3 you can follow end to end, swapping in your own subject.
Send these in order, checking the result after each one:
  1. “I track [our job applicants] in a spreadsheet with columns for [name, role, stage, and source]. Build an app that replaces it, with a sortable table and a side panel for adding and editing.”
  2. “Add accounts. My team logs in with Google, and each person sees every applicant. Give me an admin role that can also delete.”
  3. “Turn the table into a board with columns for each stage, so I can drag an applicant from one stage to the next.”
  4. “Let me attach a CV to each applicant, and use AI to pull out the name, current role, and years of experience so I can check them before saving.”
  5. “Every Monday at 9am, email me everyone who has sat in the same stage for more than 7 days.”
  6. “Add a dashboard as the home page with 4 cards for applicants per stage and a chart of applications per week.”
Send these in order, checking the result after each one:
  1. “Build a [meal plan library] where I publish [weekly plans] with a title, description, cover image, and downloadable PDF.”
  2. “Add a public landing page for people who aren’t logged in: a one-sentence headline, 3 benefit cards, and a sign-up button.”
  3. “Add accounts. Anyone can sign up free and see the 3 most recent plans. Everything older is locked.”
  4. “Let people pay [9 dollars a month] to unlock the full library, and upgrade their account automatically once they’ve paid.”
  5. “When somebody subscribes, email them a welcome message with a link to the library.”
  6. “Set the public pages up to be found in search, with clear titles and descriptions and a sitemap.”
Send these in order, checking the result after each one:
  1. “Build a tracker for [my freelance projects] with a client, a rate, hours logged, and a status.”
  2. “Add a dashboard with cards for hours this week, unbilled hours, and revenue this month.”
  3. “Every Friday afternoon, email me a summary of the hours I logged this week, grouped by client.”
  4. “Add an AI assistant I can chat with that logs hours, creates a project, and answers questions about my totals.”
  5. “When a project is marked complete, generate a draft invoice from the logged hours and email it to me for review.”
  6. “Make the whole thing work properly on my phone, since that’s where I log hours.”

Micro-prompts for polish

Small refinements take an app from working to finished. Send these to an app that’s already running, or fold a few into your first prompt for a more styled result from the start.

Motion and feedback

These add the small reactions that make an app feel alive rather than static.

Type and color

These set the visual character of the app in one line each.

Overall feel

These describe a whole personality rather than one detail.

FAQs

Here are answers to common questions about using the prompts on this page.
No. The brackets mark the parts most worth personalizing, but a prompt still works if you leave some as they are. Base44 treats whatever’s inside them as your description, so [my client projects] builds an app about client projects. Change the ones that matter to your idea and leave the rest.
Long enough to describe what you want to see, short enough to be about one thing. The prompts here are roughly the right length: a few sentences covering what it does, how it’s laid out, and anything that shouldn’t change. If your prompt covers several unrelated features, split it and send them one at a time.
Yes, apart from the ones in the starting sections, which create a new app. Everything from Adding what every real app needs onward is written to be sent into an app that’s already running.
Many feature pages include example prompts for that specific feature. The most useful ones are on creating workflows, built-in integrations, design foundations and layout, managing your app data, and setting up payments.
Yes. App templates are complete apps built by the community that you copy into your workspace and change from there. A template gets you further on the first click, and you can carry on with the prompts here from that point.

Want to write your own prompts?

The prompts here all follow the same few habits: describe what should be on the screen, say why you want it, and change one thing at a time. The prompt guide walks through each one.