Skip to content

Build your first web app

From one sentence to a published app: describe it, answer a question or two, try it in the preview, then publish it to its own address.

Last updated October 13, 2026

On this page

This walkthrough takes you from an empty page to a published app. You do not need to write any code, and nothing you do here is final: every part of the app can be changed later by asking.

Before you start

  • You need a Praxivara account. The number of web apps you can host depends on your plan.
  • Have a rough idea of who will use the app: just you, your team, or your customers. The builder will ask, and the answer decides whether the app needs accounts.

Step by step

Open Web Apps

Open Web Apps in your Praxivara workspace, at praxivara.com/user/web-apps. The Home tab asks what you will build next and offers a few starting ideas.

Describe the app in one or two sentences

Say what it is, who uses it and what they do there. For example: A booking website for my yoga studio with a weekly class schedule, member sign-up and a page for each teacher. Attach a sketch, a screenshot or a document if you have one, and press the send arrow. The Build or Discuss switch sits in the same box, so a first message can be a conversation rather than a build. See Writing a good brief for what makes a description work.

Answer the builder's questions

The builder asks only about things that genuinely change what it would build, usually who can see what. Tap an option or type an answer. Anything it wrote before asking still builds, so the preview keeps moving, and your answer starts the next turn.

Watch the preview

The preview on the right turns on when the first build compiles and refreshes on every change. You are signed in to your own app as an admin, so pages behind a login work straight away. Switch between desktop, tablet and phone widths with the buttons above it.

Ask for changes

Type what you want different: Make the schedule show a whole week, Add a teachers page, Use a warmer colour. Each message is one turn; you can queue several while a build runs.

Publish

Press Publish at the top. Check the address, choose who can open the app, and confirm. Your app is live at its address a moment later. See Publishing your app.

It keeps going on its own. A big first build takes several rounds of work. The builder carries on by itself and tells you when it has finished, with a plain summary of what you can now see and do.

What you have after this

  • An app at its own address, with pages you can click through.
  • A database with the tables the app needs, visible under Database in the dashboard.
  • Sign-in for your app's users if the app needs it, with you as the first admin.
  • A version history. Every build is kept and any version can be restored.

Good next moves

Was this page helpful?