Enterprise mobile app development: must-have features, process, and cost

Enterprise mobile app development means building an app for a company's own staff or partners: people sign in with their work accounts, the app reads and updates the company's internal systems, and the IT team decides who can use it. At Ronas IT, a cross-platform enterprise app for iOS and Android starts at $15,000 and takes at least 6 weeks, with the backend between the app and your systems and the connections to them included.
This guide is for operations leads, IT managers, and product owners who plan an app for field teams, warehouses, sales, or other staff. It covers what makes an app an enterprise app, when a ready-made tool is enough, the features an enterprise app needs, how it gets onto work phones, how we build it, what it costs, and how to choose a partner. Our cross-platform app development page describes the service itself.
What makes a mobile app an enterprise app
An enterprise mobile app is built for the people who work for or with a company, not for the public. The difference shows less in the screens than in what surrounds them.
| Aspect | Consumer app | Enterprise app |
|---|---|---|
| Users | Anyone who downloads it | Employees, contractors, or partner staff the company approves |
| Sign-in | An account the user creates | The work account the person already has, through single sign-on |
| Data | The app's own backend | The ERP, CRM, HR, and other systems the company already runs |
| Distribution | A public listing in the App Store and Google Play | A private listing for the organization, the company's device management system, or a public listing that only work accounts can sign in to |
| Control | The user decides what to install and delete | The IT team decides who can sign in and, on phones the company manages, installs and configures the app |
| Measure of success | Downloads and retention | Time saved on a task, fewer mistakes, data entered on the spot |
Common types of enterprise mobile apps
- Field service: work orders, checklists, photos, and signatures for technicians on site.
- Warehouse and inventory: barcode scanning, stock counts, picking, and receiving goods.
- Sales: client records, product information, and orders for sales reps on the road.
- Approvals and HR self-service: leave requests, expenses, timesheets, and sign-offs.
- Frontline communication: shift schedules, announcements, and task lists for staff who do not sit at a desk.
When you need a custom app and when a ready-made tool is enough
Use a ready-made tool when your process matches how the tool works and staff only need its standard screens. Build a custom app when the task is specific to your business, when people must work with several of your systems in one place, or when the tool's per-user fees grow faster than the work it saves.
- A SaaS product already covers the task: many HR, messaging, and CRM products ship their own mobile apps. If staff only need that one product on the phone, its app is the cheapest choice.
- A low-code platform fits: several vendors sell platforms for building internal apps from ready blocks. They suit simple forms and approvals over data the platform can reach, and a paid plan charges for the platform for as long as you use the app.
- A custom app earns its cost: the workflow crosses several systems, the app must work offline for a whole shift, it uses the camera, scanner, or GPS in a way a template cannot, or the data may not leave your own infrastructure.
“The first question we ask is which task gets faster, and for whom. If a tool the company already pays for can do that, we say so.”
Roman Surikov, CEO at Ronas IT
Must-have features of an enterprise mobile app
An enterprise app usually needs eight features, most of which a consumer app can skip: single sign-on, roles, offline work, integrations, support for device management, notifications that lead to an action, an audit trail, and a security baseline. Not every app needs all eight at the same depth, but each one should be decided on purpose before development starts.

1. Sign-in with company accounts
Staff should sign in with the account they already use at work, through the company's identity provider, such as Microsoft Entra ID or Okta. When someone leaves, IT disables one account, and that blocks the next sign-in. A phone that is already signed in can keep working on the tokens it holds, so the backend also has to end the person's sessions, revoke their refresh tokens, and keep access tokens short-lived, for example through OpenID Connect Back-Channel Logout, where the identity provider tells the app's backend to clear that user's sessions. Test it on a phone that is already signed in: after the account is disabled, the app should stop loading company data.
On the phone itself, after the first sign-in, Face ID or a fingerprint can unlock the app, so people do not type a password many times a shift. The app keeps its sign-in tokens in the iOS Keychain and, on Android, in storage encrypted with a key that never leaves the Keystore.
The sign-in page itself should open in the system browser, through ASWebAuthenticationSession on iOS or Custom Tabs on Android, rather than in a web view inside the app. RFC 8252, the best current practice for OAuth in native apps, requires such an external browser, because an app controls its own web view and could read the password typed into it. The same document requires PKCE, which stops another app from using an intercepted sign-in code. In the browser, the company's identity provider also applies its own rules, such as multi-factor authentication.
2. Roles and permissions
A driver, a warehouse lead, and a regional manager should not see the same screens or the same data. Roles decide which screens a person sees and which records they may change. The backend checks every request against the role, because a hidden button in the app does not protect the data behind it. On ShipMe, a shipping service app with a web version for corporate shippers, we started by outlining the user flow for each of its four roles, including corporate managers, before we designed the screens.
3. Offline work and sync
Technicians in basements, drivers between towns, and staff in large warehouses lose the connection. An offline-first app keeps the data a person needs for the shift on the phone, saves their changes locally, and sends them when the network returns. The hard part is the rule for conflicts: what happens when two people changed the same work order while offline. Decide it for each type of record before development, for example “the latest change wins” for a note and “a manager decides” for a stock count. The app should also show clearly which changes have not been sent yet.
4. Integrations with ERP, CRM, and HR systems
A sound design keeps the phone away from the ERP itself. A backend layer between them handles sign-in, access rules, and translation between the ERP's format and what the app needs. It also lets the app work from saved data when the ERP is slow or down for maintenance. If a system has no API the app can use, building one is a separate piece of work. Our guide to enterprise application integration compares the ways to connect such systems.
5. Support for device management
When a company manages its work phones through a mobile device management (MDM) system, that system installs apps, updates them, and applies the company's settings. The app has to be built and tested for this. On Android, managed configurations let the organization's IT admin “remotely specify settings for apps,” such as the server address, so staff do not type it in themselves. Ask your IT team which MDM system they use before development starts.
MDM enrollment gives the company control of the whole phone, and Microsoft notes that people are often hesitant to give that control over a personal device. For staff and contractors on their own phones, mobile application management (MAM) protects only the work app. With Microsoft Intune app protection policies, for example, IT can require a PIN to open the app, block copying its data into personal apps, and keep company data out of personal storage, all without enrolling the phone. The app takes these policies only if it integrates the Intune App SDK or goes through Microsoft's app wrapping tool, and the SDK also lets IT wipe the company data from the app while the person's own data stays. This is development work, so settle it with IT before the estimate.
6. Notifications that lead to an action
A push notification should tell a person that something needs them: a new job, an approval, a changed delivery slot. Tapping it should open that exact item, not the home screen. Keep sensitive details off the lock screen, where anyone holding the phone may see them, and let people mute the categories that do not concern them.
7. Audit trail and reports
For every change to important data, the backend should record who made it, when, and from which device. The record settles disputes about who closed an order, supports audits, and feeds the reports managers use. Those reports usually belong in the admin panel rather than in the phone app.
8. A security baseline
Company data on a phone needs a baseline of protection: no secrets in the app bundle, encrypted traffic, sessions that expire, and data scoped to each user on the backend. OWASP calls its Mobile Application Security Verification Standard (MASVS) “the industry standard for mobile app security,” and it works as a shared checklist for your security team and the vendor. Our article on secure enterprise application development covers the wider security review.
Data stored on the phone needs a decision for each type of record. On iOS, a file with the complete protection class is encrypted on disk and cannot be read while the phone is locked. Data the app has to reach in the background, such as a queue of unsent changes, needs a weaker class, so keep that data small. On Android, files in internal storage are accessible only to the app by default, and a local database with company records can be encrypted with a key held in the Keystore. On both platforms, keep company data out of cloud backups and decide what the app deletes at sign-out and on a remote wipe.
MASVS groups its controls by area: storage of data at rest, cryptography, authentication, network, interaction with the platform, code quality, resilience to reverse engineering and tampering, and privacy. Agree with your security team which groups the app is tested against. The resilience group adds the most work and fits apps whose data or functions are worth an attacker's effort.
App attestation lets the backend check that a request comes from your unmodified app on a genuine device. A script or a repackaged copy of the app cannot produce that proof. Apple's App Attest creates a hardware-based key that Apple certifies, and the app signs sensitive requests with it. Google's Play Integrity API returns verdicts on whether the binary is the one Google Play recognizes and whether the device is genuine and certified, and it expects an app installed through Google Play, which a managed Google Play private app is. The backend checks these results and decides what to block, for example an export of client records from a phone that fails the check. App Attest is not available on every device, so decide what the backend does when the check cannot run.
Compliance rules follow the data on the phone, and your lawyer decides which ones apply. The HIPAA Security Rule lists automatic logoff and audit controls among its technical safeguards, which on a clinician's phone means an app that locks after a set idle time and logs who opened which record. An app that tracks the location of field staff in the EU processes personal data, and the data minimization principle in Article 5 of the GDPR argues for tracking only during working hours and keeping the history no longer than its purpose needs.
AI features: decide where the model runs
An AI feature in a staff app, such as dictating a report instead of typing it or summarizing a long work order, starts with one decision: where the model runs, because that decides where company data goes. On iPhone, Apple's Foundation Models framework gives apps the on-device model behind Apple Intelligence, on devices that support it. On Android, Gemini Nano summarizes and rewrites text on supported phones “without needing a network connection or sending data to the cloud.” A task that needs company records or a larger model goes through your backend, with the same role checks as any other request, to a provider's API under a company account or to an open model in your own cloud.
How the app gets onto employees' phones
An enterprise app does not need a public store listing. Apple and Google both offer private distribution to one or more organizations you choose, and companies with an MDM system install apps through it. Choose the route before development starts, because it decides which developer accounts you need and how updates reach staff.

| Route | How it works | When it fits |
|---|---|---|
| Apple custom apps | The app is published privately in App Store Connect to the IDs of one or more organizations and appears in the Custom Apps section of each one's Apple Business account | Most iPhone and iPad apps for your own staff or for a set of partner companies |
| Apple Developer Enterprise Program | In-house distribution to employees through secure internal systems or an MDM system, outside the App Store | Organizations with 100 or more employees, for proprietary apps they own and develop under their own developer account, after Apple's verification interview |
| Managed Google Play private apps | The app is published in Play Console as private to one or more organization IDs and distributed through each company's EMM (device management) console | Android phones the company manages |
| Public store listing with company sign-in | Anyone can download the app, and only people with a work account can sign in | Partners and contractors who use their own phones |
Apple treats the Enterprise Program as the exception: its page limits it to use cases that App Store apps, custom apps, Ad Hoc distribution, and TestFlight do not cover. Its license agreement lets the organization authorize contractors to develop these apps on its behalf, as long as the organization owns them and they are developed under its own developer account. Custom apps still go through App Store review, and when the app holds sensitive data, Apple asks for sample data and a sign-in for its reviewers. Plan a test account for them early.
Architecture and the tech stack we choose
An enterprise mobile app is one part of a system: the phone app, a backend that owns the business rules and talks to your other systems, and usually a browser-based admin panel where managers assign work and read reports. Our default stack is React Native with Expo for the app, Laravel for the backend, and an admin panel on Laravel Backpack, or on Laravel Nova.
- Mobile app: React Native with Expo gives one codebase for iOS and Android. A native iOS app is the better choice when the app depends on iPhone hardware or on the newest iOS features. Our React Native development page lists the tools we use.
- Backend: Laravel holds the roles, the business rules, the audit trail, and the connections to your ERP, CRM, and identity provider. For live updates, such as a new job appearing on a technician's screen, we use Laravel Reverb.
- Admin panel: a web app where managers assign work, change settings, and read reports. It is part of the price of the app, not an extra platform.
- Infrastructure: the app's backend runs in your company's cloud account, and error tracking for the live app is set up there as well.
The same pattern works when the server already exists. Open MobileUI is our open-source React Native client for Open WebUI, a self-hosted AI platform. The app connects over an encrypted connection to the server the organization runs, and it is listed publicly in both stores, the last route in the table above.
How enterprise mobile app development works, step by step
An enterprise app goes through the same process as our other apps, from the scope to support after launch. We build it in sprints, usually one to three weeks long; each closes with a new build on your phone or a screen ready for review. Our engineers work with AI agents at every stage: they give the agents their tasks, write and test the code and review commits with them, own the architecture, and approve each result.
“The screens are the easiest part of an enterprise app to change later. The expensive mistakes hide in the systems behind them, such as a record that two systems both treat as their own. We look for those in the analysis phase, before anyone draws the first screen.”
Evgeny Leonov, CTO at Ronas IT
- Analysis phase, if the scope is not written yet. We map the roles, the tasks each role does on the phone, and the systems behind each task, check that every system can be reached, and write a scope document with the budget and timeline. It takes at least one week.
- Design. Designers draw the screens for each role, including the offline states and the error messages people see when a system does not answer.
- Kickoff and build. The project starts from a written kickoff plan. You agree the success criteria with the project manager, and the tech lead makes sure they can be met. Then the app, the backend, and the integrations are built in parallel.
- Quality checks. Automated tests and QA agents check every commit. After them, the code passes peer review and a team lead review, the manager checks it against the agreed scope, and you review it yourself on a staging build.
- Pilot and rollout. We recommend giving the app to one team first through the distribution route you chose, fixing what they find, and only then rolling it out to everyone.
- Support. After launch, the app needs React Native and SDK updates for new iOS and Android versions and new store rules, along with bug fixes; new features are estimated separately.
How much does enterprise mobile app development cost?
At Ronas IT, an enterprise app on top of systems you already run starts at $15,000. That one price covers the app with its design, the backend between the app and those systems, the integrations, the admin panel for managers, project management, and testing, for one client platform. The optional analysis phase is a separate choice, shown apart at the end of the example. Hosting in your cloud account starts at $200 per month. A system with no API the backend can use needs its own API, a separate project from $2,500.
| Work | When you need it | Starting price | Timeline |
|---|---|---|---|
| Analysis phase: roles, tasks, systems to connect, and a scope with the budget and timeline | Optional, if you have no written scope before the build | $1,000-$2,000 | At least 1 week |
| Enterprise app for one client platform (a cross-platform app that runs on both iOS and Android, or a single native app), with its backend, integrations, and admin panel | For the app itself; design and project management included | From $15,000 | At least 6 weeks |
| Native iOS app | Instead of cross-platform, when every work phone is an iPhone or the app depends on its hardware | The same, from $15,000 | At least 6 weeks |
| Each extra client platform, such as a native Android app, or a web app with the app's features for staff who work at a desk (the admin panel is already included) | When one app does not cover every group of users | From 50% of the first | Set by the scope |
| Backend and API: building an API for an internal system | If an internal system has no API the backend can use | From $2,500 | At least 2 weeks |
| DevOps and hosting in your cloud account | For environments, releases, and monitoring of the live system | From $200 per month | Ongoing |
For example, an app for field technicians that signs them in through the company directory and lets them read and close work orders in the ERP starts from $15,000: the app with its design, the backend, both integrations, the admin panel, and project management. Without a written scope, the optional analysis phase adds from $1,000, bringing the example to $16,000. If the ERP has no API the backend can use, building one adds from $2,500.
In an enterprise app, much of the price sits in the integrations with your systems, offline sync rules, roles, and store review.
After launch, mobile app maintenance starts at $1,000 per month for one app and covers monitoring, bug fixes, updates for new iOS and Android versions, and the releases the stores require. New features are estimated as separate work. When the system has several apps, such as a mobile app and a web app for staff at a desk, support for all of them together starts at $2,000 per month instead. The two plans are alternatives, not add-ons. Hosting runs in your own cloud account, so its bill goes to you.
How to choose an enterprise mobile app development partner
Choose a partner by what a demo does not show: how they handle store review and conflicting offline edits, who owns the code and cloud accounts, what their estimate assumes, how they communicate, what their support after launch covers, and how they use AI. Ask every candidate the same questions below and compare the answers as well as the prices.
- Distribution: how did their apps get through App Store and Google Play review? An Apple custom app for your staff goes through the same App Store review; an Enterprise Program app is installed in-house and skips it. Every React Native project we have built has launched in both stores, some after a round of changes for the reviewers.
- Offline work: ask how they would handle two edits of the same record made offline. A vague answer means the rule will be invented during testing.
- Code and accounts: where will the repositories live, and whose cloud account runs production? By default, the repository goes into your company's GitHub, Bitbucket, or GitLab account. Our GitLab is an exception, and then the contract sets when the code is transferred to you.
- Conditions of the estimate: a serious estimate says which stack, team, and third-party services it assumes. Ours comes with a page that lists them, since the scope rests on assumptions until the design is done.
- Communication: who answers you, and how fast? Our project managers answer within 24 hours on business days, and each week you get a report on what was done, what it lets your staff do, the plan for the next week, and the risks.
- Support after launch: does the monthly plan cover the whole system or only the app?
- AI in delivery: who accepts the code AI agents write, does it pass the same tests and reviews, and which AI services see your code and company data, under whose accounts? With us, the engineer who runs an agent accepts every result it produces, and the models run under company accounts, not personal ones. Our guide to picking a software vendor lists the questions to ask about AI.
Our article on mobile app development outsourcing covers the contract and the working model in more detail.
What to do next
Write down the tasks the app must make faster, the roles that do them, and the systems each task touches. Ask your IT team which identity provider and MDM system they use, and pick the distribution route from the table above. We turn that list into an estimate, and an analysis phase, if you choose it, into a scope, a budget, and a timeline.
First published 2023-12-18 by Alexander Kontsevoy, Art Director at Ronas IT. Rewritten by Alexander Storozhevsky.
Frequently Asked Questions (FAQs)
What is enterprise mobile app development?
It is building mobile apps for a company's employees, contractors, or partners instead of the public. Such an app signs people in with their work accounts, works with the company's internal systems, such as the ERP or CRM, and is installed through a private store listing, the company's device management system, or a public store app that accepts work accounts only.
What is the difference between an enterprise app and a consumer app?
The users and who controls the app. A consumer app is for anyone who downloads it, and it succeeds through downloads and retention. An enterprise app is for approved staff and uses company sign-in and company data, and the IT team controls who can use it. It succeeds when a task takes less time or has fewer mistakes.
How do you distribute an enterprise app to employees without the public app stores?
Apple offers custom apps, which are published privately to one or more organizations you specify and appear in their Apple Business accounts. Apple also runs the Apple Developer Enterprise Program, which its eligibility rules limit to organizations with 100 or more employees and to apps they own. A contractor may build such an app, but it must be developed under the organization's own developer account. On Android, a private app in managed Google Play is available only to the organizations you select. A company with a device management system installs these apps on work phones from its console.
Can an enterprise mobile app work offline?
Yes, if it is designed for offline work from the start. Each worker's shift data is stored on the device, and edits made without a connection wait in a local queue until the app is back online. The part to agree on early is the rule for records that two people changed while offline.
Should an enterprise app be native or cross-platform?
Cross-platform is our default: one React Native codebase serves iOS and Android. At Ronas IT the choice does not change the price, since a cross-platform app and a native iOS app each count as one platform; a second native app for Android adds from 50% of the first. Native makes sense when the app depends on specific hardware or on the newest OS features, or when every company phone is an iPhone.
How much does it cost to build an enterprise mobile app?
At Ronas IT, an enterprise app starts at $15,000, and that price already covers its design, the backend between the app and your systems, the connections to those systems, an admin panel, project management, and testing. A field app that signs people in through the company directory and works with orders in the ERP starts from $16,000 when the optional analysis phase comes first because there is no written scope yet. If the ERP has no API of its own, building one adds from $2,500.
How long does enterprise mobile app development take?
The optional analysis phase takes at least one week, and an enterprise app takes at least 6 weeks. Each extra role with its own screens and each system to connect adds time, and the estimate for your scope gives the timeline. A sprint usually lasts one to three weeks and ends with a test build or designs for you to review.
How do enterprise apps keep company data safe on employees’ phones?
With several layers: sign-in through company accounts, sign-in tokens kept in the iOS Keychain or in Keystore-backed storage on Android, encrypted traffic, permissions checked on the backend, and device management that applies the company's settings. The OWASP Mobile Application Security Verification Standard (MASVS) gives your security team a standard to test the app against.






