AI Builder creates micro apps from plain-language descriptions. You do not need to write or maintain code; your job is to define the goal clearly and refine the result through preview.
What to create
Start with a small, self-contained task, such as:
- organizing, transforming, or presenting a set of inputs;
- a timer, note, calculation, or reminder tool;
- a simple utility for a repeated personal workflow;
- a lightweight interactive display.
Never include passwords, access tokens, identity documents, financial records, or confidential material you do not own in a Builder request.
Write an effective description
A useful request usually covers five points:
- Goal: the problem the tool should solve.
- Audience: who will use it and in what situation.
- Inputs: what the user provides.
- Outputs: what the tool displays, creates, or saves.
- Constraints: interface, language, data handling, and safety requirements.
Example:
Create a Pomodoro timer with configurable focus and break durations. Show the remaining time and notify the user when a phase ends. Keep the interface minimal, retain the last settings after restart, and do not collect or upload usage data.
Generate and preview
- Open AI Builder.
- Enter the complete description and start generation.
- Wait for the preview instead of submitting the same request repeatedly.
- Follow a realistic user flow and note anything that does not match your intent.
The generated result is a draft. You are responsible for reviewing its content, behavior, and permission needs before saving or publishing it.
Refine with specific feedback
Change one type of problem at a time and state the current behavior, desired behavior, and success condition. For example:
Reset currently deletes all records immediately. Show a confirmation first, clear the records only after confirmation, and keep them unchanged when the user cancels.
This is more reliable than broad requests such as “make it better” or “fix everything.”
Find published walkthroughs and creation guides in the Help Center.
Preview checklist
Before saving, verify that:
- a first-time user can understand the purpose and next action;
- valid, empty, and invalid inputs all receive useful feedback;
- important actions offer confirmation or a way to recover;
- data that should persist remains after closing and reopening;
- the app does not request permissions unrelated to its main purpose;
- names, descriptions, and external links are accurate;
- text, images, trademarks, and personal information are yours to use.
Save versions
Save after each usable stage and describe the change briefly, such as “add reset confirmation” or “handle empty input.” Keep a working version before major changes so you have a stable point to return to.
Submit for publishing
Before sharing publicly:
- Choose a clear name, icon, and summary.
- Explain the main purpose, basic operation, and expected permissions.
- Complete the preview checklist.
- Confirm the content follows the Community Guidelines.
- Submit for review and track the status in creation management.
See Publishing & Review for the full workflow and Membership & Usage Limits for plan and resource limits.
If Builder cannot reach the expected result
- Narrow the scope to one primary task.
- Add concrete inputs, outputs, and failure examples.
- Continue from the most recent working version.
- If failures continue, follow Feedback & Issue Reports with the request, steps, and screenshots, excluding sensitive data.