Skip to main content
A Rork web project: the chat on the left and the finished Ember Roast website in the live preview on the right

One prompt, one project: the chat on the left, the running site on the right.

A Rork web app runs in the browser. Rork writes it with Vite and React, previews it next to the chat, and publishes it to your own address on rork.app. There is no app store, no review, and no install. You share a link, and people open it on a laptop or on a phone. Web is the right platform for a website, a dashboard, a client portal, an admin tool, or a SaaS product. It is also the fastest way to put something in front of people today. See what it builds on the Rork Web page.

​
Start a web app

Pick the platform before you send your first message. On rork.com, open the platform picker under the prompt box and choose For web. Then describe the product, not the technology.
The Rork prompt box with a coffee roastery prompt typed in and the platform set to For web

The prompt box with For web selected. The picker also offers For iPhone and For Android.

The picker says it plainly: you can add another platform later. One project can hold an iPhone app, an Android app, and a web app at the same time. See Convert your app between iOS, Android, and web.

​
Answer the questions about the look

Rork does not start writing code straight away. It asks a few short questions about the look first, and each answer is a picture, not a word. You can also type your own answer in Other.
Rork asking what overall look the site should have, with four palette options to choose from

Three questions about the look. Each answer shows the palette it stands for.

Answer all three, then press Submit. Skip this step by writing the look into your first prompt instead.

​
Approve the design, then build

Next Rork draws the screens and shows them in Design mode. Nothing is built yet, so this is the cheap moment to change your mind. Ask for a different screen in chat, or press Build to turn the design into a working site.
Design mode showing three proposed screens for Ember Roast and a Review design card with View Design and Build buttons

Design mode: the proposed screens on the right, and the Review design card with the Build button on the left.

​
Work in the project

The project has the chat on the left and a live preview on the right. The preview is the real app, not a picture, so you can click through it while you build. The controls above the preview do this:
Use Select an element for your prompt instead of describing a position in words. Point at the element, then say “make this button darker”. The agent gets the exact element and changes less around it.

​
Check the phone width

A web app has to work in a phone browser as well as on a laptop. Switch the preview size to Phone. Rork draws the site inside a phone frame, so you read the same pages at the width your visitors get.
The Ember Roast site in the Phone preview size, drawn inside a phone frame next to the chat

The same site at the Phone preview size.

Then ask for the fixes you need:

​
Publish to the web

Open Publish, then press Publish to web. Rork builds the app and hosts it at your own address on rork.app.
The Rork publish panel showing ember-roast-website.rork.app, a Site offline status, a disabled Add a custom domain row, and the Publish to web button

The publish panel before the first publish: the address, the site status, and the custom domain row.

What the panel shows:
  • The address. Rork picks one from the project name, like ember-roast-website.rork.app. Press the pencil to change the subdomain.
  • The status. It reads Site offline until you publish for the first time.
  • Add a custom domain. This row stays off until the first publish. The panel says so: “Publish the project first to add a custom domain.”
Publishing is a separate step from building. Your changes stay in the preview until you publish again, and the Publish button marks itself when the live site is behind your project.

​
Add a web app to a project you already have

Any mobile project can grow a web version. Open Project Settings → Add new app → Web, use the platform switcher above the preview, or just ask:
Each app keeps its own code. They share the chat, and the backend if you have one. A common split is a mobile app for customers and a web app as the admin dashboard.

​
What a web app cannot do

A web app runs inside the browser, so the deeply native features are out of reach:
  • No App Store or Google Play distribution
  • No home screen or lock screen widgets, no Live Activities, no Dynamic Island
  • No Apple Watch app and no Apple Health integration
  • No background tracking, and no advanced motion or body tracking
  • Push notifications are limited. On iPhone and iPad the user must add the site to the Home Screen first, on iOS 16.4 or later, and then grant permission
If your product needs any of those, build the native app and keep the web app beside it. See iPhone, Android, or web: what’s the difference.

​
FAQ

A real Vite and React project in TypeScript, styled with Tailwind. You can export it to GitHub and run it anywhere. See How to connect GitHub.
Yes. Write the look into your first prompt, and the agent has less to ask. In Design mode you can also press Build straight away.
Yes. Use Rork Cloud for a backend inside Rork, or connect Supabase or Firebase. The apps in one project can share the same backend.
Yes. Publish to the rork.app address first. The Add a custom domain row in the publish panel turns on after that.
No. Rork imports it. See Lovable to mobile app, and keep the web app in the same project.

​
Next steps

iPhone, Android, or web

What each platform is good at, and how to choose.

Add another platform

Grow the project into iOS and Android from the same chat.

Add a backend

Accounts, data, and files for your web app.

Website to mobile app

Turn an existing site into a native app.

Rork Web

The product page, with examples of what Rork builds for the browser.