How to prompt AI App Design

The Prompt tab is where you talk to the App designer. You describe what you need in plain words; it answers, and the App changes. You never write code or field names unless you want to.

Your first message: describe the work

Explain the App the way you would explain it to a new colleague: what you keep track of, who uses it, what they need to find, and what should happen by itself.

• Good: "We lend laptops to staff. We need to know who has which laptop, since when, and when it is due back. Remind the person two days before. Show me a list of laptops that are overdue."
• Less good: "Table laptops: name, user, date1, date2."

Mention the people and records your workspace already has ("linked to the client", "assigned to a team member", "for a lead"): the designer links to them instead of inventing new lists.

Small Apps and big Apps

A small App or a small change comes back in a few seconds. A large request a whole department, many lists, a long description is built step by step in the background: understanding the request, planning, designing the records, the screens, the reports and the automatic steps, then testing everything with sample data. The App list shows "Step N of M" while it works, and you get a notification when the first version is ready. You can keep working in the meantime. The Prompt tab then shows how it was built: the concept, the plan and the test results.

Refine one thing at a time

After the first version, ask for one change per message. Each one becomes a new version you can go back to.

• "Add a mileage field to cars."
• "Make the status a filter on the list."
• "Split the order form into two steps: the order, then the products."
• "When an order changes to Shipped, email the client and tell the sales team on WhatsApp."
• "Show a board of jobs by stage, and a calendar of visits."
• "Number every invoice automatically like INV-0001."
• "Add a total of the order lines to the order."

Words the designer understands well

• Stages ("new, in progress, done") become a coloured status you can filter, drag on a board and react to.
• Lines ("an order has products with quantity and price") become a table of lines inside the form.
• Totals and calculations ("the total of its lines", "price times quantity", "days between two dates") are worked out on every save.
• Reminders ("3 days before the deadline") run on that day.
• Approvals ("the manager approves the request") put Approve / Refuse buttons on the record.
• Your settings ("the email that receives orders, set by the admin") become a field on the App's Settings page.
• A connection you set up in Connect, by its name ("send each new lead to crm").

What the designer does not do

It does not write software, queries or scripts, and it does not design the printed documents (you draw those in the Documents tab; it can still say "attach the delivery note to that email"). It politely declines requests that are not about designing the App. It never changes your published App: changes stay in your draft until they are published.

When something is not right

Say what is wrong in plain words ("the status filter is missing", "the visit should belong to a job"). If a change went the wrong way, open Settings → Publish & versions and make an earlier version the current design again; your records are not touched.