Create your first app

Four moves: say it, watch it, publish it, keep it.

1. Say what you want

Open the composer and write a brief in plain language. There is no form to fill in and no template grid to choose from — a sentence or two is enough:

A class schedule and a membership form for a gym, plus a page about the trainers.

Be concrete about the things your app handles — bookings, members, articles, invoices. Those become the records your pages read and write.

2. Watch it come together

The app is assembled while you watch: pages appear, the data behind them is shaped, and the visitor sign-in is wired in. Say what you do not like and it changes — you are not waiting for a finished thing to arrive and then starting over.

Changes are shown to you before they land, as a Receipt: the list of what would be added, removed or altered. Reading it is optional; it is there so nothing appears without a record of where it came from.

Building takes minutes rather than hours. It costs Φ, the credit your plan loads each month — see Billing.

3. Publish it

Publishing puts the app at its own address and shows you the URL:

your-name.phiwebs.app

The link works immediately — share it, or put it behind a QR code. Apps published before this address existed may still answer on the older -apps.phiwebs.com form; both keep working.

On Team plans and above you can point your own domain at the app instead.

4. Keep it

The app is yours to take at any point, on every plan:

• pwpack — the app’s source in one package.
• pwapp — a ready-to-run bundle; drop it on any static host and it runs without us.

Handing the pwpack to another team installs it in their workspace like any other. Listing it on the marketplace is not open to other teams today.

Next steps

• Publishing and sharing — addresses, exports, embeds.
• Visitor sign-in — who can open your app.
• Working with surfaces — editing the pages by hand.
• Using blocks — what the pages are built from.