An open notebook with hand-drawn screens and arrows on a kitchen table at the end of the day

· 3 min read · Updated on

How do you describe your app idea to AI?

You know what your app should do, but not how to ask for it. Start with this reusable example, then answer a few questions to make your idea clearer without technical vocabulary.

To describe your app idea to AI, start with a situation you know. You can reuse this request and replace the details with those of your own work.

“I run a small repair team. On my phone, I would like to find today’s jobs, each customer’s address and the person assigned to the job. When a job is finished, I want to mark it as done so the whole team can see.”

Then add: “Start by asking me any questions you need answered, then summarise what you have understood before building. Use invented names and addresses for the first trial.”

Explain what happens today

Describe how you work without an app: a call comes in, you write an address in a notebook, then send a message to a colleague. Explain where you lose time or information.

A sentence such as “I call three people to find out who is available on Thursday” gives a clear direction. “I want to organise my business better” leaves much more room for assumptions.

Say who should see what

Name the people who will use the tool: you, your colleagues, your customers. Explain what each person should be able to view or change.

For example: “The technician sees their jobs, but not the invoices. I see the whole team’s schedule.” These are working rules; you do not need to know their technical translation.

Show an example with invented information

Draw a screen on paper or prepare a small table with two fictional jobs. Circle the information you want to find first.

If you use a work document as a model, make a copy and replace names, contact details and other confidential information before sharing it. Keep only the layout and the details that help explain your idea.

Choose one thing to try

Start by asking only to add a job and find it in the schedule. Quotes, payments and automatic reminders can wait.

Also describe a situation that causes trouble: “If I do not have the address yet, I want to see that it is missing.” You will then have something specific to check in the first version.

Review what the tool has understood

Ask for a short summary: who the app is for, what it should do and what will wait. Correct an inaccurate sentence before moving on; an attractive page can hide a misunderstood need.

In Maestro, this clarification happens through a conversation, followed by documents you review and approve. A specification is simply the document describing what needs to be built; here is how to review it in ten minutes.

You can start with three sentences

Write: “Today, I do…”, “I would like to be able to…” and “What must never happen is…”. Add an example, then let the person or tool helping you ask questions.

You can give this description to AI or a developer. To expand it later, follow our guide to preparing your specification.

Read the complete guide: build an application without coding

Back to the journal

Take the baton.

Leave your email to try Maestro in the first waves.

The beta is open by invitation on macOS 13 and later. Leave your email for an upcoming wave of access. Windows is in development.

The beta is currently available on macOS 13 or later. Your answer helps us plan other versions.

Your email is only used to let you know when access opens. Nothing else, we promise.