How to properly prompt my app?
To get the best results from Fuzen’s AI when building your app, write clear and specific prompts. Here are a few tips: Be clear about the type of app you
The quality of your Fuzen app depends heavily on how well you describe what you want. The AI is powerful, but it works best when you give it clear, specific instructions. Here is how to write prompts that get great results.
Start building on the Fuzen dashboard. A detailed, specific prompt in the chat box produces a much better first draft.
The anatomy of a great prompt
A strong prompt includes four elements:
- What type of app you are building (CRM, school management, HR, project tracker, etc.)
- Who will use it (roles: admin, teacher, student, sales rep, customer)
- What features it needs (pages, forms, dashboards, workflows)
- How data should flow (what happens when a form is submitted, who gets notified, what triggers what)
Examples: Vague vs. Specific
| Vague prompt (poor results) | Specific prompt (great results) |
|---|---|
| "Build me a CRM" | "Build a CRM for a real estate agency. It should have: a Leads page with name, phone, email, property interest, and status fields. A Deals pipeline page showing deals in stages (New, Negotiation, Closed Won, Closed Lost). A dashboard showing total leads this month, conversion rate, and revenue. Two roles: Admin (sees everything) and Agent (sees only their own leads)." |
| "I need a school app" | "Build a school management system with these modules: Student enrollment (name, class, parent contact), Attendance tracking (daily, class-wise), Fee management (fee structure, payment tracking, receipts), and a Parent portal where parents can see their child's attendance and fee status. Roles: Principal (full access), Teacher (attendance + their class only), Accountant (fees only), Parent (read-only for their child)." |
| "Make an HR tool" | "Build an HRMS with: Employee directory (name, department, designation, joining date, salary), Leave management (apply, approve, balance tracking), Attendance (check-in/check-out with timestamps), Payroll (monthly salary calculation based on attendance and leaves). Roles: HR Admin, Department Manager, Employee." |
Prompting tips
- Be specific about fields. Instead of "a customer page", say "a Customers page with fields: Company Name, Contact Person, Email, Phone, Industry, Annual Revenue, and Status (Active/Inactive)."
- Name your roles. The AI needs to know who can see what. Always list the roles and what each one should access.
- Describe workflows. "When a leave request is submitted, notify the manager by email. The manager can approve or reject. If approved, deduct from the leave balance automatically."
- Use real-world examples. Reference tools you have used before: "Like Zoho CRM but simpler" or "Similar to Google Classroom but with fee tracking."
- Iterate, don't overload. Start with the core features in your first prompt. Then add complexity one feature at a time through the AI Chat Canvas.
The AI Chat Canvas. After your app is built, use this editor to iterate — describe changes and the AI applies them instantly.
After the first draft
Once the AI generates your app, open it and explore every page. Then use the AI Chat Canvas (click the widget > Edit With AI) to refine:
- "Add a search bar to the Employees page"
- "Make the Dashboard show a chart of monthly revenue"
- "Only Admins should be able to delete records"
- "Add an email notification when a new lead is created"
- "Change the color scheme to dark blue and white"
Common mistakes to avoid
| Mistake | Why it hurts | Better approach |
|---|---|---|
| Too vague ("build me an app") | The AI has to guess everything -- results will be generic | Name the app type, features, and roles |
| Too much at once | Overwhelming prompts can lead to missed features or errors | Start with core features, add the rest iteratively |
| No roles mentioned | Everyone gets the same access -- no privacy or security | Always define at least 2 roles with different permissions |
| Ignoring data relationships | Pages become disconnected silos instead of a connected system | Describe how data connects: "Each Invoice belongs to a Customer" |
Was this article helpful?
Related articles
How should I test my app before going live?
Before sharing your app with real users, it’s important to test it thoroughly. Here’s a checklist: 1. Test all user flows Go through every action a
Read articleWhat are best practices for structuring my app's data?
Good data structure makes your app faster, easier to maintain, and easier to expand. Here are the key principles: 1. Separate concerns into distinct collections
Read articleHow can I improve my app's performance?
Here are some tips to keep your Fuzen app fast and responsive: 1. Limit records shown on list pages Don’t load 10,000 records at once. Set a default filte
Read article