Here's where the magic happens. In your first message, you describe what you want to build, and an initial version of your App is generated for you within minutes.
The quality of what you get back depends a lot on the quality of what you put in. Clear prompts lead to better results. Think of it like briefing a thoughtful colleague: the more clearly you explain what you need, the closer the first draft will be to what you had in mind.
When writing your prompt, it helps to include:
What you want your App to do, including any specific features or functionality. For example, "a form where employees can request time off, with fields for start date, end date, and reason."
Whether the App should use real data, and whether it should connect to an existing story. (We'll go deep on connecting to workflows in the next module, so for your first App, it's fine to keep things simple.)
The intended look and feel. You can describe the design direction in words, or upload mockups and references to guide the style.
Whether you want endpoints generated for you. If you mention this in your prompt, the builder can handle it automatically. Again, don't worry about this yet, it's there when you need it.
So, a strong first prompt might read something like:
"Build a simple event registration App with a clean, modern look. It should have a form where people can enter their name, email, and the session they'd like to attend, plus a confirmation message after they submit."
Notice how that prompt covers the what (an event registration form), the look and feel (clean and modern), and the key features (specific fields and a confirmation message). That's a great starting point.
🖐️ Try this: Build a Hello World App
New to emulations? Swap between watch, try, or scroll mode.