Does an employee app have to be publicly available in an app store?

On this page

An employee app does not have to be publicly available to everyone in an app store. It can be distributed to specific organizations; on iPhone, an approved direct-link option is also available. Decide separately who can install the app and what their business account allows them to access. Private distribution alone does not define employee permissions within the application.

Make this decision before the first production release. List the devices, user groups and person responsible for installation support. The development team and administrator can then check which channel fits your business environment. Our separate guide explains who should own app publishing accounts and the responsibilities at handover.

Who uses the app, and who owns the phones?

A business with company phones and an administrator starts from a different position than a team using personal devices. For company phones, check the existing device management arrangements. For personal phones, record which work settings employees must accept and how business access is separated from personal use.

MDM and EMM refer to systems an organization uses to manage devices and apps. If your business already uses one, involve its administrator in the distribution decision. If it does not, ask for setup and support to be identified separately in the proposal. Buying an app does not automatically include that work.

Include occasional contractors, business partners and shared phones used across shifts. For each group, record the operating system, sign-in method and tasks. Identify anyone who cannot install the proposed release before development begins.

How do public, private and direct-link distribution differ?

Three separate decisions for an employee app: who can install it, what a business account permits and how access is revoked.
Installation, business permissions and access removal need separate checks.

Apple distinguishes public and private distribution. Private apps are offered to organizations specified in App Store Connect through Apple Business or Apple School Manager. Switching between public and private after approval requires a new app record and another submission. Check the distribution method before release.

An Apple unlisted app is available through a direct link without appearing in ordinary store searches or listings. It can include unmanaged personal devices, subject to Apple review and approval of this distribution method. Anyone who obtains the link can download it, so business sign-in and permissions still need to be implemented within the system.

On Android, managed Google Play supports private apps restricted to specified organizations. User distribution works with an EMM environment. Check the organization identifier and supported distribution process with your administrator and provider.

Scroll the table sideways to see all columns.

What to check when choosing employee app distribution
ApproachWhen to consider itWhat to agree
Public app with business sign-inPublic availability of the installation fits the purpose.Who issues accounts and what an unauthorized user sees.
Private Apple distributionThe recipient has the appropriate business environment.Recipient organizations and the app assignment process.
Apple unlisted direct linkA limited audience also uses unmanaged devices.Approval, installation instructions and business sign-in.
Private managed Google PlayAndroid users belong to specified organizations.EMM support, organizations and the responsible administrator.
Business web appThe required tasks can be completed in a browser.Testing the required features on actual phones and connections.

The Apple Developer Enterprise Program has specific eligibility rules and is intended for qualifying internal employee apps. Do not plan it as a general channel for clients or business partners. Check the program requirements before including it in a proposal.

Example: field teams and an occasional partner

Imagine a company assigning work orders to its own teams and occasionally hiring a partner. This is a fictional planning example. Employees use company Android phones, while the partner brings a personal iPhone. Both need to open an assigned job and send a report.

The company and its administrator investigate private managed Google Play for their devices. For the partner, they first check the recipient organization and installation requirements on a personal phone. If the chosen iPhone channel does not fit, they consider approved unlisted distribution or browser access according to the features the job requires.

The pilot must cover both groups. A demonstration on the development team's phone is insufficient. The partner should complete the intended installation, receive an individual account and see only assigned work. The administrator then checks whether that access can be removed when the engagement ends.

What protects business data after installation?

Specify what the installed app shows before sign-in, how employees receive accounts and what their roles allow. Moving departments or changing shifts may require different permissions without reinstalling the app. The business system should check permissions when data is accessed.

Agree on procedures for a departing employee, a lost phone and a session that is already open. Ask for access removal to be tested, including a direct request to the system. A hidden button or a promise to delete the app leaves an important part of the requirement unresolved.

Disabling an account does not mean every previously downloaded copy has disappeared from a phone. List the data stored locally and what remains possible without a connection. Our guide to offline business applications can help define this scope, alongside agreed storage and synchronization checks.

Can a test build replace production distribution?

TestFlight is for beta testing and gathering feedback. Apple states that a build can be tested for up to 90 days. Plan ongoing employee use through an appropriate production channel, with a separate process for testing updates.

At handover, agree who prepares an update, who checks it and how employees learn that a new version is required. Check compatibility between the older app and the business system as well. Some team members may not install an update on the same day.

How should distribution be checked before rollout?

Choose trial users and devices representing every intended group. Record the app version, device, installation channel, expected result and actual outcome for each attempt. The following is a proposed acceptance checklist, not a report of tests already performed:

  1. A new employee receives an account and installs the app from the instructions without access to development accounts.
  2. A user without business approval cannot open another person's work orders even after receiving the installation link.
  3. A partner sees only the agreed work, and a role change updates the accessible data.
  4. The administrator removes access and checks the existing session and the next connection attempt.
  5. A replacement phone completes installation, and the agreed procedure addresses data on the lost device.
  6. An update completes the main task, with a check for users still running the previous supported version.

For phones shared across shifts, add sign-out and sign-in by another employee. Test a connection interruption if it is within scope. An unsuccessful attempt should provide a clear explanation and a support contact rather than relying on informal instructions known to one person.

What should you prepare for an employee app estimate?

Send the number and types of user groups, operating systems, phone ownership and existing business management arrangements. Add the main task, offline requirements and how accounts should be issued and removed. These details determine the distribution and support scope.

If the product choice is still open, first compare a mobile app with browser access. For business mobile app development, we plan distribution alongside features and maintenance. Request an estimate with an outline of users and devices; passwords and employees' business data are not needed for the initial discussion.

YOUR NEXT PROJECT

We listen. We analyze. We deliver.

Free project estimate