Web, PWA or App Store: where a personal app should live

For an app only you or a few people use, the web or a Home Screen web app is usually enough. Here is when the App Store is worth its fee and review.

Tomas·5 min read
0places an app can live
iOS 0Home Screen sites open as web apps by default
$0a year for the store route

If an app is for you, your family or a small team, put it on the web and add it to the Home Screen. Since iOS 26, any site added to the Home Screen opens as a web app by default, and since iOS 16.4 those web apps can send push notifications. The App Store is worth its yearly fee and review only when strangers need to find the app, or when it needs device features the web can't reach.

This is the default we chose for Leanfinit's beta: Publish puts your app live on the web. Here is the reasoning, so you can decide for your own app.

Three places an app can live

A web app runs in the browser from a link. Anyone with the link can open it on any device. There is no install, no review and no fee to a store.

A Home Screen web app, often called a PWA, is the same web app saved to the Home Screen. It gets its own icon and opens in its own window, without the browser's address bar.

A store app is a native build distributed through the App Store or Google Play. People find it by searching, install it, and get updates through the store.

For a personal tool, the question isn't which is best in general. It's which of the three costs least while still doing the job.

What changed on iPhone

For years the honest answer was "the web is fine on Android, weaker on iPhone." That has shifted, as of November 2026:

Push notifications: iOS and iPadOS 16.4 added Web Push for Home Screen web apps. The site must be on the Home Screen, and it has to ask permission after a direct tap, such as a "remind me" button (WebKit).
Badges: the same release added the Badging API, so an icon can show a count, like unpaid bills or tasks due.
Install by default: in iOS and iPadOS 26, "every website added to the Home Screen opens as a web app" unless the user turns off "Open as Web App." A manifest is no longer required (WebKit).

For most personal apps, such as a habit log, a medication schedule or a shared chore rota, these cover what people used to install a native app for.

What the App Store costs you

A store app adds three costs that a personal app rarely earns back.

Money. The Apple Developer Program is $99 a year (Apple). Google Play is a one-time $25 (Google).

Review. Apple's Guideline 4.2 rejects apps that don't go beyond "a repackaged website" (App Review Guidelines). Guideline 4.2.6 rejects apps from an "app generation service" unless the content owner submits them. A simple personal tool can fail both for reasons that have nothing to do with whether it's useful to you.

Time. New personal Google Play accounts must run a closed test with at least 12 testers for 14 consecutive days before going live (Google). That's two weeks and twelve people for an app you might be the only user of.

We wrote more about these obstacles in Why most Apple developers never ship.

When the store is the right answer

Choose a store app when at least one of these is true:

People need to discover it. If strangers should find your app by searching, the store is where they search.
It's a product, not a tool. You plan to charge for it, support it and grow it.
It needs device access the web doesn't give. Deep background work, some sensors, or tight integration with system features still favour native.
A client asks for a listing. Then it's their app and their account; see whose accounts should publish client apps.

If none apply, the store is overhead.

A quick way to decide

If your app is…Put it…
For you aloneOn the web, saved to your Home Screen
For family or a small groupOn the web; share the link
For staff of one businessOn the web first; a store build if staff need offline device features
For the public, to be found and installedIn the stores

Our insight on PWA vs native for personal use goes deeper on the technical trade-offs, and making an app for yourself without publishing to the App Store walks through the personal case.

How this fits Leanfinit

During the beta, Leanfinit does not submit apps to the App Store or Google Play. Publish puts the app live on the web, which covers the first three rows of that table. What happens when you press Publish explains the details.

Generated apps keep their data on the device, with no backend by default. On the web, that means each person's entries stay in their own browser rather than on our servers. The trade-off: data doesn't move between your phone and laptop on its own. For a personal tool that lives on one phone, that's usually the right trade.

If the app later needs a store listing, code export is available. The app is built on Flutter, which targets both iOS and Android.

What I'd do with a new personal app

Publish it to the web, add it to your Home Screen, and use it for two weeks. If you still open it every day and wish it did something the web can't, then consider the store. Many personal apps never reach that point, and that's not a failure. It means the cheapest home was the right one.

Describe your app and publish it: studio.leanfinit.com.