Building your first app

This walkthrough takes you from an empty prompt to a live, working app.

1. Start a new project

Open the Apps tab in app.nexrall.com and tap + New Project.

2. Describe what you want

Be as specific or as loose as you like — the agent will ask a clarifying question if something important is ambiguous. A good first prompt usually includes:

• What the app does — "a habit tracker", "an internal inventory tool".
• Key screens or actions — "a list view and a form to add items".
• Anything it must integrate with — "send me an email when someone submits the form".

Example:

"Build me a simple habit tracker: a list of habits, a button to mark today done, and a streak counter for each habit."

3. Watch the agent build

You'll see the agent work in real time:

• Files being written and edited.
• Commands it runs (installing packages, running tests).
• A live preview of the app as it takes shape.

A build typically finishes in a few minutes for a small app. Larger requests may take longer or span multiple messages — the agent will tell you if it's splitting the work into stages.

4. Try the live app

Once a build finishes, the app is deployed to its own URL immediately. Use it like a real user would — that's the best way to find what to refine next.

5. Keep refining by chatting

Nothing about the app is "final" after the first build. Send another message in the same session:

"Add a dark mode toggle"

"The streak counter should reset if I miss a day"

Each message is another turn of the same agent, working on the same project, with full memory of what it already built. See Editing by chat for tips on getting good results from follow-up requests.

Tips for better first results

• One clear ask beats a giant spec. Start with the core flow, then layer on details in follow-ups — the agent handles iterative refinement well.
• Mention constraints up front if you have them ("must work on mobile", "no login required").
• If something looks wrong, say so plainly. "The delete button doesn't work" is enough — you don't need to diagnose the bug yourself.