How to Write a Prompt That Gets the App You Want

Every message you send Snapp costs credits. A clear message usually gets it right the first time; a vague one turns into three or four rounds of guessing. The difference is rarely effort — it's knowing what the AI needs to hear.

Here are six habits that save the most credits.

---

1. Say what the app is before what it should do

The single most common reason Snapp stops and asks a question is that it can't tell what kind of app you want.

❌ "Build me an app that lets people connect" ✅ "Build a dating app where people create a profile, swipe through others, and chat when they match"

One sentence naming the app type and its three main actions is enough to start. You can refine everything else later.

2. One change per message

It's tempting to write a list. But when you ask for five things at once, the AI has to prioritise and it will guess wrong on at least one — and you pay for the whole round.

❌ "Change the colors, add a filter, fix the login, and make the profile photo round" ✅ "Make the profile photo round"

Small messages are also cheaper individually, so a wrong one costs less.

3. Name the screen

Snapp apps have screens. Saying which one removes almost all ambiguity.

❌ "Add a search bar" ✅ "On the Explore screen, add a search bar at the top that filters the list by name"

4. Describe the result, not the implementation

You don't need to know how it's built. You do need to say what you should see when it works.

❌ "Use a useState hook to store the toggle" ✅ "Add a switch in Settings that turns notifications off, and remember the choice when the app reopens"

If you're not a developer, this is good news: plain language beats half-remembered technical terms.

5. When something breaks, describe what you see

"It doesn't work" forces the AI to hunt. Three details — where you were, what you did, what happened — usually get a fix in one round.

❌ "Login is broken" ✅ "On the login screen, I enter my email and password, tap Sign In, and nothing happens — the screen stays the same"

Screenshots help too.

6. Connect your database before asking for real data

Until your app has a database, everything it shows is sample content. Asking for "save the user's profile" before connecting one means the AI builds a demo version — and you'll pay again to rebuild it for real.

Connect Supabase first, then ask for the features that store data. It's the single biggest source of repeated work we see.

---

The 30-second checklist

Before you hit send, check your message answers these:

What kind of app is this? (first message only)
Which screen does this change affect?
What should I see when it's working?
If something broke: what did you do, and what happened instead?

You don't need perfect English or any technical vocabulary. You need to be specific about the outcome. That's the whole skill — and it's worth learning early, because it's the difference between building your app in ten messages instead of thirty.

How to Write a Prompt That Gets the App You Want