Mobile app development for iOS and Android
Native iOS and Android apps in Swift and Kotlin. Including an honest answer about whether you need native at all.
AMT (Advanced Millennium Technologies) is a mobile app development company that builds native iOS apps in Swift, native Android apps in Kotlin, and cross-platform apps where that is the better choice. We build enterprise and consumer mobile apps, including field apps designed to work without a network connection.
Trusted by
// how_to_decide
Native vs cross-platform vs mobile web: how to decide
Most agencies have a house answer they are selling. Here is the actual decision, and the third option is a real one.
| Factor | Native | Cross-platform | Mobile web |
|---|---|---|---|
| Best when | The app uses the device heavily (camera, Bluetooth, background location, offline sync, biometrics) or the app is your product. | Mostly screens and forms on top of an API, on both platforms, with a small team. | Occasional use, no device features needed, and you want one thing to maintain. |
| Cost | Two codebases, but roughly 1.6 to 1.8 times one platform, not double, because design and backend are shared. | One codebase, with some platform-specific work at the edges. | The cheapest by far, with no app store releases. |
| The catch | Two release cycles and two sets of platform changes. | Device-heavy features and deep OS integration get expensive, and you find out late. | No push notifications in the same way, no store presence, weaker offline support. |
| Honest note | Right more often than budget-led decisions assume, especially for field apps. | Right for many enterprise apps. | Often the right answer for internal tools, and rarely proposed because it is the smallest project. |
If your app is mostly screens on top of an API and nobody will use it in a basement, you may not need an app. That is an uncomfortable thing for an agency to publish, and it is true often enough to say.
Get the native vs cross-platform decision on one page
The comparison with the questions that settle it, including the do you need an app test. Built for the meeting where engineering and finance want different answers.
// cost_drivers
What really drives mobile app development cost
- The backend. If it does not exist, or was not designed for mobile, it is most of the project, and it is often missing from the first quote.
- Offline behaviour. An app that works without a network is very different engineering from one that shows a loading spinner.
- Device features. Camera, Bluetooth, background location and biometrics each add platform-specific work plus permission and privacy handling.
- App store review and release. Plan real calendar time for it, especially the first submission.
// security_checklist
Enterprise mobile security checklist
| Control | Why it matters |
|---|---|
| Sign-in through your identity provider (SSO) | Staff use one account, and access ends the day someone leaves. |
| Device management support (MDM) | IT can push, configure and wipe the app on company and personal devices. |
| Encrypted local storage | Data on a lost phone stays unreadable. |
| Secure token handling | Sessions cannot be copied off the device. |
| Certificate pinning | The app only talks to your real servers. |
| Minimal data on the device | Less to lose if a device is lost, which matters most for field apps. |
// mobile_services
Mobile app development services
| Service | What it covers |
|---|---|
| Native iOS app development | Swift, current platform standards, built to pass App Store review the first time where possible. |
| Native Android app development | Kotlin, tested across the devices and OS versions your users actually have. |
| Cross-platform apps | Ionic or React Native, where one codebase is the better choice. |
| Field apps | Offline-first, for people working where the network is not. See logistics. |
| Enterprise mobile apps | Connected to your internal systems, with sign-in that fits your identity provider. |
| Backend for mobile | The part that is usually the real project. |
| App store submission and release | Including the first submission, which is always the slowest. |
// proof
Proof
Last-mile delivery apps for a German electric vehicle manufacturer. Native iOS and Android apps on one multi-tenant SaaS platform: a white-label consumer app for each delivery business, a rider app for pickups and drop-offs with route guidance, and a web dashboard for each operator. The rider app opens and closes smart locks on the cargo boxes over Bluetooth. AMT owned the full lifecycle, from product design and architecture to release and ongoing maintenance.
// app_cost
How much does a mobile app cost?
| Scope | Typical effort | What drives it |
|---|---|---|
| App on both iOS and Android | Medium to high | Backend complexity and offline needs, more than the number of screens. |
| Single platform | About 60% of the above | Design and backend are shared, so one platform is not half the cost. |
| Mobile web | Low | No app stores and no release cycle. |
| Typical budget range | 20 to 30 USD per hour | Native or cross-platform, the number of platforms and backend integrations. |
// not_right_fit
When we are not the right fit
// faqs
FAQs: mobile app development
Should we build a native or cross-platform app?
Which cross-platform frameworks do you use?
How do you secure an enterprise mobile app?
How much does it cost to develop a mobile app?
How long does it take to build a mobile app?
Can the app work offline?
Who handles App Store and Google Play submission?
Tell us what the app has to do
30 minutes with an engineer. We will tell you whether it needs to be native, and whether it needs to be an app at all.
Not ready to talk? Read how we deliver. No form.