How to build a mobile app for your company? Stages, roles and app store requirements
The mobile app development process for a company, step by step: needs analysis, technology choice, design, development and testing, App Store and Google Play developer accounts, release and maintenance. With store requirements checked against Apple and Google documentation.
A company mobile app is built in seven stages: needs analysis and first-release scope, technology choice, interface design, development with testing, setting up developer accounts, release on the App Store and Google Play, and maintenance after launch. Some of the work on the company side does not depend on the contractor: an organization account in both stores requires a D-U-N-S number, and Apple also requires the company to be a legal entity. Before release, data handling has to be described in App Store Connect and Play Console and, if the app lets users create an account, users have to be able to delete it. Time and budget depend on the scope of the first release, the number of integrations and whether the app has to run on iOS and Android from day one.
The short answer
Sources checked on 19 November 2026.
This guide is for the person in a company who is responsible for a new mobile app for customers, partners or employees and wants to understand the whole process before asking contractors for proposals.
In short: start with one user problem and the scope of the first release, not with a feature list. In parallel with design, set up the company's developer accounts on the App Store and Google Play, because organization verification needs documents a contractor cannot prepare for you. Plan device testing and time for store review, and include maintenance after release in the budget.
1. App development stages in one table
The table shows what is produced at each stage and what is needed from the company. The stages partly overlap: developer accounts are set up during design, and testing runs throughout development.
| Stage | Output | What the company provides |
|---|---|---|
| Needs analysis | Problem, users, first-release scope, list of integrations | A decision-maker, access to users and data about the process |
| Technology choice | Decision: native or cross-platform, backend, integrations | Information about the systems the app has to connect to |
| Interface design | User flows, wireframes, clickable prototype | User feedback and scope sign-off |
| Development and testing | Working test builds on iOS and Android | Testers on the company side, test data, API access |
| Developer accounts | Organization account in the Apple Developer Program and Google Play Console | D-U-N-S number, entity details, company domain and website |
| Release | The app on the App Store and Google Play | Descriptions, screenshots, privacy policy, data declarations |
| Maintenance | Updates, fixes, usage measurement | A product owner and a budget for further releases |
The following sections describe each stage and the store requirements that affect the schedule.
The project involves: a product owner on the company side who decides on scope, a UX/UI designer, mobile app and backend developers, and a tester. One person can combine some of these roles, depending on the scope.
2. Needs analysis and first-release scope
The first stage answers three questions: who will use the app, what problem it has to solve and how the company will know it works. The output is a short description of the users, a list of the key flows, for example placing an order, booking a visit or reporting on a customer visit, and success measures.
This stage also produces the list of integrations: ERP, CRM, payments, sign-in, notifications. Integrations affect the project scope and risk, so it helps to know them before the estimate. If the company system has no API, or the API is undocumented, preparing it is a separate piece of work.
The first-release scope should cover only the flows needed to check whether users actually use the app. Further features are easier to add once there is usage data. Who should do this work, an in-house team or an external company, is covered in our comparison of an in-house team and an agency.
3. Technology choice: native or cross-platform
An iOS and Android app can be written separately for each system or as one codebase in a cross-platform technology. The React Native documentation describes it as a way to create native apps for Android, iOS and other platforms using React.
The choice depends on a few conditions. If the app has to run on both systems and the team knows React or TypeScript, one codebase can simplify development and maintenance, although that benefit depends on the project scope. If the app relies heavily on features of one system, for example advanced hardware access, test those features in a prototype before deciding.
This stage also settles the backend: whether the app uses the company's existing systems through APIs or needs its own server layer for sign-in, notifications and combining data from several sources.
4. Interface design and prototype
Design starts with user flows, not with how the screens look. For iOS, the reference point is Apple's Human Interface Guidelines, which describe navigation patterns, controls and accessibility principles on Apple devices.
For Android, that role is played by Material Design, Google's design system with components and guidance for Android apps. An app built from one codebase can share a design, but system elements such as back navigation should behave the way users know from their system.
A clickable prototype is shown to a few future users before development. A fix in a mockup can cost less than changing a finished screen, depending on the scope of the change, and a test with users shows whether the first-release scope is right.
5. Development and device testing
Development is split into short iterations, each ending with a build the company can install and check. Testing covers automated code tests, flow tests on devices running both systems and integration tests against company systems with test data.
iOS test builds are distributed through TestFlight. According to Apple's TestFlight page, up to 100 team members with roles in App Store Connect can be added as internal testers, and up to 10,000 people can be invited as external testers, with the first build for external testers going through App Review.
On Android, testing runs on testing tracks in Play Console. For new personal accounts these are a release prerequisite, which the next section covers.
6. The company's developer accounts on the App Store and Google Play
A company that wants the store to show its name as the seller publishes the app from an organization account. According to Apple's Developer Program enrollment page, a sole proprietor or single-person business can enroll as an individual, but then the account holder's personal name is shown as the seller instead of the company name. For an organization account, Apple requires the organization to be a legal entity that can enter into contracts with Apple and to have a D-U-N-S Number, a work email address on the company's domain and a functional public website.
Google Play also requires a D-U-N-S number for an organization account. Google's page on choosing a developer account type states that the number is used to verify the organization's identity and that applying for it with Dun & Bradstreet is free.
The account type affects the schedule. According to the Google Play testing requirements, developers with personal accounts created after November 13, 2023 must run a closed test with at least 12 testers who have been opted in continuously for at least 14 days before release. Google's page describes this requirement for personal accounts. An organization account also goes through verification, including the D-U-N-S number, so it is worth setting it up early in the project.
7. Release: store requirements before the first version
Before submission for review, the app has to be complete. Section 2.1 of the App Store Review Guidelines requires a final version with all necessary metadata and fully functional URLs, without placeholder text, tested on-device.
Both platforms require a description of data handling. According to Apple's App Privacy Details page, information about privacy practices, including the practices of third-party partners whose code is in the app, is provided in App Store Connect and is required for new apps and app updates.
On Google Play, the equivalent is the Data safety section. According to the Play Console help on the Data safety section, the developer completes a form about privacy and security practices, and the information is shown on the app's store listing.
If the app lets users create an account, it also has to let them delete it. This is required by Apple's guideline 5.1.1(v) and by the Google Play policy described on the page about account deletion requirements, which also requires a web link to request deletion.
An Android app published on Google Play has to target a current API level. According to the Google Play target API level requirements, the requirement does not cover permanently private apps restricted to users in one organization and intended for internal distribution only. For other apps, starting August 31, 2026 new apps and app updates must target Android 16 (API level 36) or higher, with lower thresholds for Wear OS, Android Automotive OS, Android TV and Android XR. Existing apps covered by the requirement must target at least Android 15 (API level 35), with lower thresholds for Wear OS, Android TV, Android XR and Android Automotive OS, to remain available to new users on newer system versions.
The full list of things to prepare before submitting to the stores, from screenshots to test accounts for reviewers, is in our App Store and Google Play launch checklist.
8. After release: maintenance and budget
Release starts the next stage. iOS and Android get new versions, stores change their requirements, such as the target API level on Google Play, and the libraries in the app need updates. Without maintenance, after some time the app may stop meeting the store's requirements, for example the target API level for further updates.
After launch, measure whether users complete the key flows defined in the analysis stage and plan further releases on that basis. The budget therefore covers not only the first release but also maintenance and further development.
What the cost of the first release and of maintaining a React Native app consists of is covered in our guide to React Native app development cost in 2026.
Frequently asked questions
- How long does it take to build a mobile app for a company?
- The time depends on the scope of the first release, the number of integrations with company systems and whether the app launches on both systems. Add time for developer account verification, store review and, for a new personal Google Play account, at least 14 days of closed testing. A reliable schedule needs a scope and integration analysis first.
- Does the company need its own App Store and Google Play account?
- Yes, if the store should show the company as the seller. An organization account in the Apple Developer Program and on Google Play requires a D-U-N-S number. A contractor can publish the app on the company's behalf once given access to the account, but the account and the entity details belong to the company.
- Does the app have to be built separately for iOS and Android?
- Not necessarily. Cross-platform technologies such as React Native let you create native apps for both systems from one codebase. Separate apps make sense when key features depend on the capabilities of one system. Check this in a prototype before deciding.
- What does the company need to prepare before the app is released?
- Organization developer accounts, the app description and screenshots, a privacy policy, data handling declarations in App Store Connect and in the Data safety section in Play Console, and, if the app lets users create an account, a way to delete it. The app submitted for review has to be complete and tested on devices.
Let's talk about your app
Tell us who will use the app and which systems it has to connect to, and we will help you set the first-release scope and the stage plan.
Content updated: November 19, 2026
Google Preferred Sources
See GMI more often in Google
Add gmi.software as a preferred source. Google may highlight our new articles more often in Top Stories and supported AI experiences.