Your business already has an app. It is sitting in your website
Most small companies do not need to build an app from scratch. Their website already does everything the app would do. What has changed is how quickly — and how cheaply — that site can become a real, installable Android app.
The gap between a working website and an app on a customer’s phone is now measured in days, not months.
Ask a small business owner why they do not have an app and the answer is usually the same: it costs too much, it takes too long, and they would need to keep two systems running. All three used to be true. None of them is true any more.
A growing share of small apps are not written line by line. They are built around a website that already works, wrapped in a native shell that gives it an icon, a place on the home screen, offline handling and notifications. Update the website and the app updates with it. There is nothing extra to maintain, because the app and the site are the same thing.
Stage one: the shell
Most small apps today are not written from scratch. They are built around a site that already works. A native shell provides the icon, the splash screen, the offline handling and the notification plumbing; the existing site provides every screen the user sees. Change the website and the app changes with it, without a new release.
The four stages between a working website and a live store listing.
Services such as Native App AI, which convert a website to an app, have reduced this stage to a form: an address, an icon, a colour, a package name. What comes out is an installable APK for testing and a signed Android App Bundle for the store.
It is worth understanding the difference, because it causes confusion later. The APK is the file you send to a colleague to try on their phone. The bundle is the file the store accepts. They are not interchangeable, and uploading the wrong one is the first rejection many publishers meet.
Stage two: the signing key
Every Android app is signed with a key that proves updates come from the same owner. This is the single most consequential file in the process and the one most often treated casually. Lose it, and you cannot publish an update to your own app — not with an appeal, not with a support ticket. The listing survives; your ability to change it does not.
Anyone using a conversion service should establish, before paying, whether they receive their own signing credentials or whether the provider retains them. Both arrangements are workable. Not knowing which one you have is not.
Stage three: the declarations
This is where the calendar starts slipping. Google Play asks for a privacy policy at a permanent, publicly reachable address; a data safety declaration describing what the app collects, why, and whether it is shared; a content rating questionnaire; and a target audience statement. If the app sends notifications, uses a camera, or takes payments, each of those has to be accounted for.
The declarations must match what the app genuinely does. Reviewers compare them against the app’s behaviour, and a mismatch is treated as a misrepresentation rather than an oversight. A wrapped website inherits whatever its site does — analytics, chat widgets, embedded payment forms — so the honest answer is often broader than the owner expects.
Stage four: testing, then the listing
New individual developer accounts face an additional requirement: a period of closed testing with a group of real testers before the app can be released publicly. For a business with staff and regulars, finding testers is straightforward. For a solo founder with no network, it is the single longest delay in the process, and it cannot be skipped by paying more.
The listing itself — title, description, screenshots — is the part customers actually judge.
Only then does the listing matter: a short title, a description, a feature graphic and screenshots taken on a real device. This is the part customers see and the part most publishers rush. A clear description of what the app does for an existing customer converts better than a list of features, and it sets expectations that keep the review score healthy.
The five-minute glossary
| Term | What it means in practice |
| APK | A single installable file. Useful for testing, or for handing an app directly to staff and customers outside a store. |
| Android App Bundle (AAB) | The packaging format Google Play requires for new apps. The store builds the right version for each device from it. |
| Signing key | The credential that proves later updates come from the same owner. Lose it and you cannot update your own app. |
| Closed testing | A private release to a small group of testers, required for new individual developer accounts before public launch. |
| Data safety form | A declaration of what the app collects and shares. It must match the app’s actual behaviour. |
Where it usually goes wrong
- Uploading an APK where the store expects a bundle, then assuming the app was rejected on quality grounds.
- A privacy policy hosted at a temporary address that stops resolving a month later.
- A data safety form filled in from memory rather than from what the site actually loads.
- No signing key backup, discovered at the first update rather than at launch.
- Leaving closed testing until last, when it is the requirement with the longest fixed duration.
- A store description written for investors rather than for the customer holding the phone.
What it is reasonable to expect
Handled in the right order, a converted app is genuinely quick. The build is an afternoon. The declarations are an hour if the answers are gathered first. The testing period is the only stage with a floor you cannot lower, and it runs in the background while you prepare the listing.
The same route applies whether the site is a hosted shop, a booking page, or a WordPress site turned into an Android app — the shell differs hardly at all, and the store requirements do not differ by a word.
The honest summary is this: the technical barrier to putting a small business on a phone home screen has effectively gone. The website you already pay for is most of the app; what remains is an afternoon of setup and a little preparation. For most small companies, the question is no longer whether they can afford an app. It is why they would keep asking customers to type in a web address.