Operations wants an app so field technicians can log visits, take photos and get the customer's signature. Three proposals come in. One offers two native apps, another a single cross-platform app, and the third says a well-built web app will do. All three make good arguments, and none of them asked whether there's any signal on site.
Enterprise mobile app development starts with a decision worth making before you ask for quotes: native, hybrid or web. Make it too late, or let the vendor make it based on what they happen to be good at, and the bill shows up later, as maintenance, rewrites, or an app nobody uses because it fails exactly where it's needed most. Here is a practical way to decide based on your users, offline work, integrations and what it really costs to keep a corporate mobile app published.
Three paths for a corporate app
| Native app | Hybrid or cross-platform app | Web app or PWA | |
|---|---|---|---|
| How it's built | One codebase for iOS (Swift) and another for Android (Kotlin) | One codebase for both platforms, for example with Flutter | A website that installs to the home screen |
| Hardware access | Full, and new features arrive first | Almost full, with some native plugins | Limited to what the browser allows |
| Offline work | Solid | Solid | Possible, but more fragile |
| Distribution | App Store and Google Play, or private channels | Same as native | A URL, no stores |
| Maintenance | Two teams or two codebases | One codebase | Same as the website |
"Hybrid" gets used for very different things. An app built with Flutter or React Native compiles into a real app that ships through the stores. A website wrapped in a container is something else, and it's usually the one that gives hybrid its reputation for being slow. When a vendor says "hybrid", ask which one they mean.
Web apps have improved too. Since iOS 16.4, web apps added to the home screen can receive push notifications. For simple forms or lookups, that may be enough, and you skip the stores entirely.
Five questions that decide the technology
In our experience, the choice comes down to these questions, and rarely to technical taste:
- Who uses it, and on what phone? If they're employees with company-issued devices, you control the hardware. If they're customers, you have to support whatever they bring, including five-year-old models.
- Does it have to work without signal? Warehouses, mines, farms and basements are everyday locations in Chile. An app that stores data on the phone and syncs when the connection returns needs a local database and rules for resolving conflicts. That shapes the architecture more than the programming language does.
- What hardware does it use? Every option handles the camera and GPS well. Industrial barcode scanners, Bluetooth printers, NFC or biometrics for signing push you toward native or cross-platform.
- Which systems does it connect to? The app is almost always the visible face of an ERP, a CRM or a legacy system. If that system has no API, someone has to build one, and that work is the same whatever mobile technology you pick.
- Who will maintain it three years from now? Two native codebases need iOS and Android specialists. A single cross-platform codebase is cheaper to sustain, as long as the team knows it.
If the answer to the second or third question is "yes", rule out web. If none of them demands something very platform-specific, a cross-platform app is usually the sweet spot for a mid-sized company.
Publishing to the stores: costs that don't appear in the quote
Many quotes stop at development. A published app has recurring costs and obligations that continue after launch.
Developer accounts are the cheap part. The Apple Developer Program costs USD 99 per year and Google Play charges a one-time USD 25 registration fee. Everything else is where the money goes:
- Store requirements change every year. Since April 28, 2026, Apple requires apps to be built with Xcode 26 and the iOS 26 SDK to upload them. On Google Play, from August 31, 2026, new apps and app updates must target Android 16 (API level 36). If nobody keeps the app current, one day you won't be able to ship even an urgent fix.
- Every release goes through review. A rejection over a misread policy can delay by days a change the business needed yesterday.
- Commissions apply if you sell digital content inside the app. On Google Play, developers in the reduced tier pay 15% on the first USD 1 million each year and 30% on anything above that. An internal app, or one that sells physical goods, usually isn't affected, but check before you design the payment model.
- Signing keys, certificates, store accounts and access should all be in your company's name. If the store account belongs to the vendor, the app isn't really yours.
Apps used only by your employees don't need a public listing. Apple says that for most organizations the right route is the Developer Program with private distribution through Apple Business. The Apple Developer Enterprise Program, at USD 299 per year, requires at least 100 employees and is only meant for cases those channels can't handle.
Security and personal data on the phone
Phones get lost, get lent out and mix personal data with company data. A corporate app has to account for that from the start: sign-in with the corporate identity, encryption for anything stored locally, and a way to wipe company data without touching the user's own.
If your company runs Microsoft 365, Intune can apply app protection policies, such as requiring a PIN or blocking copy and paste into personal apps, even on phones that aren't enrolled. For your own app to receive those policies, it has to integrate the Intune App SDK or be wrapped with the App Wrapping Tool. Settle that before choosing a framework, because not every combination takes the same effort to integrate.
Then there's Law 21,719, Chile's new data protection law. An app that captures national ID numbers (RUT), location, photos or signatures processes personal data. On October 28, 2026, the Senate approved postponing the law's effective date to October 15, 2027, and the bill moved to the Chamber of Deputies. Until it's published as law, the date is still December 1, 2026. For an app you'll use for years, that changes little: consent, minimal permissions and access logs belong in the first version.
Native, hybrid or web: what we recommend
No single answer fits everyone, but there's a sensible order to think it through:
- Web or PWA when it's a lookup or a simple form, users have good connectivity and you'd rather avoid the stores.
- Cross-platform when you need offline work, camera, GPS or notifications on iOS and Android, and want one team maintaining it. This is what we recommend most often for field, sales and service apps.
- Native when the app depends on very specific hardware, demanding performance, or features that land first on one platform.
Before deciding, also look at what it costs to build and maintain the rest of the system. In custom application development cost we explain what drives the budget. If part of the process is used by customers on a computer, custom web development in Chile covers when a portal makes more sense.
Frequently asked questions
Is a hybrid app slower than a native one?
It depends on the kind of hybrid. A compiled cross-platform app, like one built with Flutter, performs well for the vast majority of business uses. Apps that just wrap a website in a container tend to feel slower.
Can I distribute an app only to my employees without publishing it in the stores?
Yes. On iOS, Apple offers private distribution through Apple Business. On Android, check with your IT team about the private distribution options in the device management tool you already use. The app still has to follow each platform's rules, even if the public can't see it.
How much does it cost to maintain a corporate mobile app?
More than most budgets assume. Beyond developer accounts, plan for yearly updates to meet Apple and Google requirements, support, backend infrastructure and improvements. Ask for those costs to be estimated in the proposal from day one.
Let's talk about your app
At Disrupsoft we build custom mobile apps for iOS and Android with Flutter, integrated with the systems you already use, and we work with you from the first idea to delivery. If you're weighing an app for your team or your customers, let's review your mobile app development project.
