When someone tells me they need an app, they often mean something in a pocket: orders, clients, payment, an alert. Not necessarily an App Store icon. Stores mean reviews, fees, and a round trip for every small change. For a business still figuring out who the user is, that can eat budget before there is a product.
I build web apps and PWAs: open from a link, add to the home screen, Hebrew, talk to your server. I wrote about that choice in PWA vs app stores. If there is a real reason for a store (in-app payments, an audience that lives there), we say so. I will not sell you native because it sounds expensive.
What you get
A mobile UI you do not pinch-zoom. Auth. Permissions. A hook to payments or a WhatsApp bot if that is part of the business. Your code, not an account in an app builder that shuts down on a Tuesday. If you already have a site, sometimes the app is the site. Sometimes marketing stays separate. We decide from who taps, not from a buzzword.
When I say no
If you barely have users, and nobody will test on their phone this week, the store can wait. First something live that does one job well. People do not like hearing that from an app developer, so I say it early.
Questions
Do you ship to Google Play and the App Store?
We can talk about it when there is a business reason. Default is a strong web app. Stores add time and fees. If you truly need them, we understand why, instead of slapping an icon on a slide.
Will it feel like a phone app?
A PWA can sit on the home screen, run fullscreen, and send notifications within what the browser and server allow. That is not always identical to native. For most businesses I meet, it is enough, and cheaper to keep alive.