Your first app, end to end

Luminax builds software by conversation. You describe the thing; an agent plans it, writes it, runs it in a real sandbox, looks at the result with its own eyes, and fixes what it got wrong. This page is the whole loop, in order, with nothing skipped.

The nine-minute path

1. 1
   Write one honest sentence

   Say what the product is and who it is for before you say how it should look. "A booking page for a two-chair barbershop, with deposit payments" beats "a modern responsive site" every time.

2. 2
   Let the project prime

   While you are still reading your own sentence, Luminax has already created the project row, cloned the starter repository, and opened a sandbox. There is no build step for you to wait on.

3. 3
   Watch the agent plan

   The first reply opens with a short plan: what it will build, what it will defer. Read it. Correcting a plan costs one sentence; correcting a finished app costs an afternoon.

4. 4
   Let the tool calls stream

   File writes, reads, searches, browser captures and image generation all appear as live cards. You can leave the page — the run belongs to the server, not your tab.

5. 5
   Look at the preview

   The preview panel boots the real app, not a screenshot. Click through it while the agent is still working.

6. 6
   Correct in small strokes

   One change per message lands cleaner than five. "Make the hero calmer and drop the second CTA" is fine; a twelve-item list is a queue, not a message.

7. 7
   Add the backend when you need it

   Ask for accounts, a database table, or file uploads and Cloud is provisioned in place — tables, row-level policies and grants written for you.

8. 8
   Publish

   Publishing gives you a public address immediately. Attach your own domain whenever you like; the old address keeps working.

What to do when it goes sideways

• Preview blank? Open the details panel and read the last tool call — nine times out of ten it names the file it broke.
• Reply feels generic? You under-specified. Add the constraint you were holding in your head.
• Wrong direction entirely? Roll back to any earlier state instead of arguing your way forward.
• Stuck mid-run? Pause. The transcript is durable; nothing you have already seen is lost.