Hype StackHypeStack

How to Create an App for a Website: Three Routes Compared

GuideThe answer first, the product second.

All stacks

By Maciej Pyrc, who maintains Hype Stack.Updated .

Most people asking this do not need an app built. They need their existing website to behave like one, which is a much smaller job and sometimes takes an afternoon.

If you already have a website and want an app for it, there are three ways to get there and they differ by roughly two orders of magnitude in effort. Choosing the cheapest one that meets your actual requirement is the entire decision.

We sell source code you clone and run yourself. This page answers the question first, and the product section is at the end where you can skip it.

The three routes

Installable web app
Wrapped web app
Native app
What it is
Your site, installable to the home screen
Your site inside an app shell, in the stores
A separate application built for each platform
Effort
Hours to days
Days to weeks, plus store review
Months, and permanently thereafter
App store presence
No
Yes
Yes
Push notifications
Yes on Android, and on iOS when installed
Yes
Yes
Device features
Camera, location, offline; not much beyond
Same, plus whatever the wrapper exposes
Everything

Start at the left and move right only when a specific requirement forces it. The two requirements that genuinely force a move are needing to be in an app store, and needing a device capability the browser does not expose.

The free version first: make the site installable

Adding a web app manifest and a service worker turns a website into something a phone will install to the home screen, launch without browser chrome, and open offline. This is a real capability rather than a trick, and on a modern site it is a small amount of work.

What installable actually requires

  1. Serve over HTTPS

    A requirement rather than a recommendation. Service workers do not register on an insecure origin.

  2. Add a web app manifest

    A small JSON file naming the app, its icons, its theme colour, and how it should display. This is what makes the install prompt appear and what the home screen icon comes from.

  3. Register a service worker

    A script that sits between the page and the network. Even a minimal one that caches the shell makes the app open instantly and survive a dropped connection.

  4. Decide what works offline

    This is the design question, not the technical one. Reading cached content offline is straightforward; accepting input offline means a queue and a sync rule, which is real work.

    Where the effort actually goes

On iOS the install is done by the user through the share menu rather than prompted, which is worth knowing before you plan around it.

When you need the app stores

Being in the stores is a distribution and credibility decision more than a technical one. Some audiences look for an app and will not install from a browser, and some organisations require a store listing before they will adopt something.

If that is the requirement, wrapping is the middle route: your web app runs inside a thin native shell that can be submitted to the stores. Capacitor is the common choice for this and it is an open source project, theirs rather than ours. Two things to know before committing. Store review has rejected apps that are purely a website in a shell with no added value, so plan for at least push notifications or offline behaviour. And you take on the release cycle, meaning a store submission for updates that used to be a deploy.

When native is genuinely justified

Background location, Bluetooth peripherals, heavy offline data, tight camera control, or performance that a browser cannot reach. Also anything where the app is the product rather than an alternative way to reach a website.

If none of those apply, native is a large ongoing commitment bought for reasons that will not survive the first year of maintenance.

The mistake worth avoiding

Building the app as a separate product with its own backend. Whichever route you take, the app should talk to the same API as the website, or you have two systems that drift and two places to fix every bug.

That is the practical argument for deciding your API boundary before you decide your app strategy: a site whose data comes from a typed API can be wrapped, installed, or given a native client later, while one that renders everything on the server has to be partly rebuilt for any of them.

Where this stack fits

If you already have a website, none of the above needs us; make it installable and see whether that is enough.

If you are earlier than that and the app is part of something you are building, this stack is a React frontend and a Hono backend with a typed client between them, which is the boundary described above. The native app shell layout pack covers the shell for a desktop-style application, and the notifications pack handles in-app and email notifications, though push to a phone is a separate integration you would add.

There is no mobile app in the box, no wrapper, and no store submission tooling. What there is is the API boundary that makes any of the three routes possible later, plus accounts, organizations, billing, and an admin app.

Below are the templates and packs. If your question was how to get your existing site onto a home screen, the manifest and service worker above are the whole answer and you can stop there. The free favicon generator makes the icons and the manifest file from one logo.

The broader question is in How Do I Make an App? Four Routes, Ranked by Cost, and the full build route in How to Build a Web App, Decision by Decision. When the answer is a real mobile app, How to Create a Mobile App From a Website walks the three routes.

What is Hype Stack?

Every product starts with the same month of work nobody pays you for: sign-up and login, teams and permissions, taking payments, notifications, an admin panel to run the business. Hype Stack is that month, already built and tested. Start from the free open-source app, add the pieces you need with one command, and keep going on the part that is actually your idea.

Everything lands as real code in your own repository, so there is nothing to rent and nothing anyone can switch off. For the engineers: React 19, Hono, Postgres, and a desktop build, typed end to end.

See it running.

Curated starters built on this stack: a layout, feature packs, a theme, and bonus pages. The previews are recordings of the real apps.
See all 8 templates

Packs in this stack.

Real source code across frontend, backend, and admin. The ones this stack installs come first; the rest compose in later.
SaaS Starter (WorkOS)StarterAuthentication, organizations, roles, sessions, and a full admin app, powered by WorkOS.CalendarFeatureA working calendar: five views, drag to reschedule, event invites, and working hours.Cookie ConsentFeatureA cookie consent banner and preferences modal built on vanilla-cookieconsent, themed to your tokens and translated through your message catalog.Billing (Polar)FeaturePolar integration, subscriptions, billing flows, and an admin revenue widget.
See all 20 packs

Two ways to install.

Same features underneath. Either command resolves what the packs need, copies the source into your repo, and merges the Prisma schema.

Take a template

A landing page, a design system, a themed layout, and the features already wired in. Rebrand it, put your product in the middle, ship.

$npx @hype-stack/cli template
Browse templates

Compose your own design

Your design and your choices, without rebuilding auth, billing, or notifications. Tick the packs you want and the CLI wires them into the open-source starter.

$npx @hype-stack/cli compose
Browse packs

Questions, answered.

Make it installable, which is hours to days and puts it on the home screen but not in a store. Wrap it in a native shell, which is days to weeks plus store review and gets you a store listing. Or build native, which is months and permanent. Start at the left and move right only when a specific requirement forces it.

More stacks.

Your SaaS is one sentence away.

Add a Pro plan at $19 a month with a 14-day free trial.. Let customers invite their team and choose who can do what.. Send a welcome email the moment someone signs up.. Show me which customers are close to their limit this month.. Let people sign in with Google.

Free to start. Works in the AI tool you already use.