Write a useful brief
Name your audience, the main task, and the screens you need. Add sample content, your preferred language, and a visual direction. Start with one complete journey rather than every possible feature.
A practical guide from your first brief to a published app.
Name your audience, the main task, and the screens you need. Add sample content, your preferred language, and a visual direction. Start with one complete journey rather than every possible feature.
Read the proposed approach, then use the preview to check each screen. Ask for focused changes with the screen name and expected behavior. Use the code editor or visual editing controls when appropriate.
Use workspace settings to manage your database and app secrets. Keep private keys out of prompts and frontend code. Test signed-out access and permissions before storing real customer information.
Test navigation, forms, empty states and error messages. Check the smallest phone layout and keyboard navigation. Generated code needs your review; a successful preview is not a security or production-readiness guarantee.
Open Publish in your project and check the deployment status. You can connect a domain you own, or use the available domain checkout. Registration, DNS and HTTPS can remain pending after payment; follow the status and the exact DNS records shown in the project.
Yes. Explore the editor opens a public demo. Create an account to save your own projects and start building.
The core interface supports English, Arabic, French, Spanish and Portuguese. Some advanced screens and legal pages are still in English. You can describe your app in your own language.
Check Pricing for current plans and credits. App AI usage and domain purchases are separate from coding-plan allowances. Review the amount, period and renewal information in checkout before paying.