Web first, then PWAs

Make your website installable before you make it native.

You built a web app. Now you want it on a phone's home screen, with an icon, opening full-screen like a real app. Good news: you probably don't need a “real app” at all. The ladder from website to app store has four rungs, and most people should climb only the first one or two.

This chapter is rung one, and it's the one we point almost everyone to: the PWA.

What a PWA is

A Progressive Web App is just your website with a little extra configuration that lets a phone install it. Visitors tap “Add to Home Screen” and get an icon that launches full-screen, with no browser bar, an app-style splash screen, and (if you set it up) offline support and push notifications. It is still your one website underneath, so there's no second codebase to maintain.

Turning your app into one is close to free:

Make this a PWA: add a web app manifest with an icon and name, set it up to work offline, and make it installable to the home screen on iOS and Android.

Why start here

• –No app store, no fees, no review. It ships the instant you deploy to Vercel. No $99 account, no waiting on Apple, no rejection risk.
• –One codebase, every device. The same project is your website and your installable app. Fixes and features go out everywhere at once with a single push.
• –It covers most “I need an app” cases. For a tool, a tracker, a dashboard, or a content app, a PWA feels genuinely app-like and nobody notices the difference.

The honest limits

PWAs can't do everything a native app can. Deep hardware features, rock-solid offline behavior, and rich push notifications are still stronger in a true native app, and Apple keeps PWA support on iOS a little more limited than Android. Most importantly, a PWA does not live in the App Store, so if being findable there matters to you, you'll want a later rung. But reach for those rungs only when a real limit forces you to, not by default.

AI Clubhouse · Vibe Coding Guide