Distributing an app without a public store listing

Why would you not want a public listing?

Three reasons, all legitimate. The app was written only for employees and downloading it from outside is meaningless. Its screens expose business processes, pricing structure or dealer information; sitting on a public page is a commercial leak. Or the app only works on specific device models and gives the general user a poor experience.

In all three cases the right answer is not to leave the store entirely but to use the store's distribution infrastructure with listing switched off. Signing management, update delivery and device compatibility then stay on the normal path — you do not have to build your own infrastructure.

The routes on each store

On Apple, a custom app is distributed to specific organisations through Apple Business Manager: the app goes out over App Store infrastructure but does not appear in search, and only the named organisation can access it. On Google, Play Console's private app option does the same job — the app appears only in the targeted organisation's managed Play experience.

On both routes the app goes through review. That is the most commonly missed point in planning: being internal does not remove the review time, it only changes who can see the result.

Why is direct APK distribution narrowing?

Google is making verification of developer identity mandatory for apps installed on certified Android devices. This is a layer separate from reviewing an app's content: verifying who published it. The requirement is coming into force in stages, and its real impact is on those distributing outside Play.

The practical consequence: if you have built a setup that hands an APK to a dealer network, a field team or corporate devices, put into your plan that this setup will require a verified developer identity. If you publish through Play Console, identity verification was already completed as part of registration.

Device ownership decides the setup

Two scenarios. If the device belongs to the company, installing the app, forcing a version and removing it when needed can all be done through management, with no step required from the user. If the device is the employee's own, a work profile setup is needed: company apps and data live in a separate space and the personal side stays outside management.

The distinction is as much legal as technical. What the company can see and what it can erase on a personal device is something the employee has to be told in writing — the obligations around processing personal data continue here too.

Where does the cost actually sit?

Not in the app but in the inventory and enrolment process. On a two-hundred-person field team the real work is not writing the app; it is building a repeatable answer to who has which device, which version is installed, how a new joiner installs it and how a leaver is removed.

So the first week of an enterprise distribution project should go to the device inventory. A route chosen before the inventory exists is usually the wrong one: manual installation that works on a ten-device pilot collapses at the first update across two hundred.