Custom Mobile Apps for Companies: Cost, Timeline, Native vs Cross-Platform
A custom mobile app for a company is a dedicated iOS and Android application built for a specific process: technicians' field work, sales reps' orders, customer bookings, or service requests. In this article I explain when a mobile app makes sense (and when a website is enough), what makes up the cost, how long delivery takes, whether to choose native or cross-platform, and what to prepare before talking to a vendor.
When a company needs a mobile app and when a website is enough
A mobile app makes sense when…
- people work away from a desk: service, installation, field sales, logistics
- you need the camera, GPS, barcode scanner, signature, or offline mode
- customers return regularly (bookings, orders, status), so an icon on the screen has value
- you want push notifications instead of emails nobody reads
A website or PWA is enough when…
- the user works rarely and always has coverage
- the process is mostly forms and browsing data
- the budget is limited and you want to quickly validate the idea
- you do not need a presence in the App Store / Google Play
Native, cross-platform, or PWA: what to choose
For most business apps I recommend cross-platform (React Native): one codebase runs on iOS and Android, cutting build and maintenance cost by 30-40% compared with two native apps. Access to the camera, GPS, scanner, push notifications, and offline mode is complete.
I choose native technology (Swift, Kotlin) when the app relies heavily on hardware (Bluetooth for industrial devices, AR, video processing) or when it is a consumer product where every performance detail matters.
A PWA (a web app installed on the phone's home screen) is a good first stage if you want to validate the process without app store publishing. Limitations: weaker notifications on iOS, limited offline mode, no access to some system features.
How much a custom mobile app for a company costs
Single-role MVP
from PLN 12,000 net
5-8 screens, one role (e.g. technician), backend, a simple office panel, one integration. 3-5 weeks.
App with panel and roles
about PLN 25,000-45,000 net
Several roles, offline mode, photos and signatures, 2-3 integrations, admin panel with reports. 6-8 weeks.
System with a customer app
estimated after analysis
Customer app + team app + panel, payments, notifications, ERP integrations. Delivered in stages.
What drives the cost
Number of screens and roles
An app for a technician (5-8 screens) costs less than a system with roles: technician, dispatcher, customer, administrator.
Offline mode
Syncing data after regaining coverage, conflict resolution, queuing photos - a significant part of the work in field apps.
Integrations
CRM, ERP, inventory, calendar, payments, courier systems. Each integration means API analysis and error handling.
Backend and admin panel
A mobile app needs a server, a database, and an admin panel for the office. This is often half the budget.
Security
Login, permissions, on-device data encryption, GDPR - mandatory with customer data.
Publishing and maintenance
Developer accounts (Apple USD 99/year, Google USD 25 one-off), store review, updates for new OS versions.
How long delivery takes: stages
Analysis and mockups (1 week)
Who uses the app, in what conditions, what data it collects, what it connects to. A clickable screen prototype to discuss with the team.
Backend and integrations (1-3 weeks)
API, database, authentication, connections to company systems. The admin panel in parallel.
Mobile app (2-4 weeks)
Screens, offline mode, camera, GPS, notifications. Tests on real devices, including older ones.
Publishing and pilot (1-2 weeks)
Developer accounts, store assets, Apple/Google review, a pilot with a few users, fixes.
In total: 3-8 weeks for the first version in the stores. The most time goes not into screens but into integrations and edge cases (no coverage, wrong data, permissions).
Publishing in the App Store and Google Play
- Developer accounts are created for the company (not the vendor), so the app belongs to you.
- Apple requires a privacy policy, a description of collected data, and a test account for the reviewer. Review usually takes 1-3 days.
- Internal apps (employees only) can be distributed without the public store: Apple Business Manager, Google Play private distribution, or an install link.
- After launch the app needs updates 2-4 times a year for new iOS/Android versions - include it in the maintenance budget.
Brief checklist: what to prepare before talking to a vendor
- Who will use the app and in what conditions (office, field, shop floor, customer at home)?
- Which 3-5 actions must be possible in the app for it to be useful from day one?
- Is offline mode required?
- Which systems must the app connect to (CRM, ERP, spreadsheet, calendar, payments)?
- Who in the office should see the data and in what form (panel, report, notification)?
- How many devices and which (iOS, Android, both, tablets)?
- What is the rough budget and deadline?
You do not need a specification. Answers to these questions are enough for me to prepare a clickable prototype and an estimate. If you wonder whether AI can build such an app on its own, read Is AI Enough to Build a Website or App?
Considering a mobile app for your company?
Describe the process the app should handle. I come back within 2-5 days with a clickable screen prototype and an indicative estimate - free of charge. You can also first ask the AI advisor whether an app, a PWA, or an automation fits your case better.
Frequently Asked Questions
How much does a custom mobile app for a company cost?
A single-role mobile app MVP starts from PLN 12,000 net. An app with an admin panel, roles, offline mode, and several integrations usually costs PLN 25,000-45,000 net. Larger systems are estimated in stages.
How long does it take to build a mobile app?
The first version in the stores usually takes 3-8 weeks: analysis and mockups, backend and integrations, the app, publishing and pilot.
Native or cross-platform?
For most business apps, cross-platform (React Native) gives one codebase for iOS and Android at a lower cost. Native makes sense with heavy hardware use or in consumer products.
Can a mobile app work without coverage?
Yes. Offline mode with synchronization after regaining coverage is standard in apps for field employees, but it increases the scope and budget.