Create a useful app

Start with the work, not the software

Describe the job you want help with. You do not need to choose a database, framework, screen layout, or technical feature.

A good first request answers four questions:

1. Who is it for? “My studio,” “our front desk,” or “just me.”
2. What should it help with? Inventory, projects, bookings, notes, or another kind of work.
3. What information matters? Names, dates, quantities, status, notes, or totals.
4. What should feel easy? Finding overdue work, entering a new item, or seeing what needs attention.

Use a right-sized first request

Create a simple studio supply list. I need an item name, quantity, low-stock warning, and notes. Make it calm and easy to scan.

This is enough to make a first version that can be tested. It does not attempt to predict every report, permission, or edge case.

Keep the first version small

Start with the workflow you will try today. Add separate ideas later.

For example, build the supply list before asking it to order from vendors, read receipts, predict usage, notify a team, and synchronize devices. Each addition introduces more behavior to review and may require account, folder, or private-key access.

Mention important boundaries

Tell Zymorph when a requirement truly matters:

• “This is used on a shared front-desk computer.”
• “Do not include prices.”
• “The list must work when the internet is unavailable.”
• “I only want this app to read the selected folder, not change files.”

Do not assume every requested behavior is available offline. Creating/changing the app needs the selected model provider, and external accounts require a separate connection.

Try the result as a user

Before asking for more features:

1. add realistic sample information;
2. complete the main task from beginning to end;
3. close and reopen the app if saved data matters;
4. check empty, long, and unusual values;
5. notice the one thing that would make the workflow easier.

Then use Improve an app to request the next change.