Three refine tips that double the quality of your AI-built app
One sentence makes the app. The refines make it actually useful. Here's how to get the most out of them.
Three refine tips that double the quality of your AI-built app
The first build gets you 70% of the way there. Refines get you the last 30%. Almost nobody uses them well on the first day. Here are three patterns that consistently produce better apps.
1. One change per refine
The single biggest mistake: piling five changes into one refine prompt.
"Add a status column with red/amber/green badges, add a search bar, change the title font to bold, and make the date column sortable."
The AI will try all four. Three will work. One will silently get dropped. Sometimes two. You won't know which.
Instead, refine one thing at a time:
- "Add a status column to the Orders sheet with values 'New', 'Processing', 'Shipped', 'Delivered'."
- "Show the status column as colored badges — green for Delivered, amber for Processing, blue for Shipped, slate for New."
- "Add a search bar above the orders table that filters by customer name."
- "Make the date column sortable."
Each refine takes ~60 seconds. Total: 4 minutes. Result: every change applied correctly, app working at every step.
The opposite of this — five changes in one prompt — takes maybe 90 seconds but you have a 40% chance of needing to start over.
2. Name the field, name the value
The AI gets confused when you say "make it look better." It does not get confused when you say specific things.
Bad refine prompts:
- "Make the form prettier."
- "Improve the dashboard."
- "Add validation."
Good refine prompts:
- "Make the amount input right-aligned, with a $ prefix, and only accept numbers with 2 decimal places."
- "On the dashboard, add a card at the top showing the total revenue this month vs last month."
- "Require that the customer email field contains an @ before allowing the form to submit."
Every refine that mentions a specific column, a specific value, a specific behavior will work the first try. Every refine that uses vague aesthetic language will be hit or miss.
3. Build for the workflow, not for you
If you're the only user of your app, refine prompts that describe your workflow. ("Show me which orders need to be packed today.")
If your team will use it, refine prompts that describe their workflow. ("When a driver opens the page, show only their assigned deliveries for today, sorted by stop number.")
The AI is much better at building role-specific views when you describe the role first.
Try this two-step pattern:
- First refine: "This app has three user types — admin, dispatcher, and driver. Add a simple login screen that asks for the user's name and role." (Demo auth — not real auth, but enough for an internal tool.)
- Second refine: "When the role is 'driver', show only the deliveries assigned to that driver name. When the role is 'dispatcher', show all deliveries with assignment dropdowns. When the role is 'admin', show the full table with all controls."
You'll get a role-aware app on the third refine. The AI does the conditional rendering. You don't write a line of JavaScript.
Bonus: when to start over
Sometimes the app you built isn't the app you want. The schema is wrong, the relationships don't make sense, the UI is fighting your workflow. Don't refine your way out of that.
Open a new build. Type a tighter, more specific prompt. Ship it in 90 seconds.
The cheapest thing in the AI app builder world is throwing away an app and building a new one. Refines compound — five thoughtful refines turn a good app into a great one. But five refines fighting an architectural mismatch turn it into something nobody wants to use.
Rule of thumb: if you're three refines in and still working around the schema, delete and restart with a better prompt. You'll get there 10× faster.
What we're working on
- Diff-based refines — only the changed part of the HTML gets re-emitted. Goal: 30-second refines.
- Refine suggestions — based on what you've built, the AI proposes the three most impactful refines you could try next.
- Component library — curated mini-modules ("paginated table", "kanban board", "stats strip") you can request by name.
Build your first app. Then come back and try these three patterns.
— Ahmed