A native app is software written specifically for one operating system, such as iOS, Android, Windows or macOS, using the tools that platform's maker provides. You download it from an app store, it lives on your device, and it can use the phone's hardware directly.
What makes an app "native"
On iPhone and iPad, native apps are written in Swift (or the older Objective-C) with Apple's SDKs, usually in Xcode. On Android they are written in Kotlin or Java with Google's Android SDK. The compiled app talks to the operating system without a browser in between, so it gets the platform's own buttons, gestures, notifications and settings screens, plus direct access to the camera, Bluetooth, GPS, health sensors and file storage.
The cost is duplication. An app for both iPhone and Android traditionally means two codebases, two sets of tests and two app store submissions, each with its own review rules and fees. That is why hybrid and cross-platform frameworks exist.
A concrete case: a gym's check-in app
A gym chain wants members to scan in with their phone, get a reminder when a class is about to start, and unlock a locker over Bluetooth. Reliable background notifications and Bluetooth hardware access are exactly where native development is strongest, so a native app is a reasonable choice. The same gym's class timetable and membership sign-up could still be ordinary web pages.
Should a local business build a native app?
Usually not at first. People rarely install an app for a shop or service they use a few times a year, and every install starts with convincing them to visit the store and tap "Get". A fast website or web app reaches them with a link. Native apps start to pay off when customers return often (ordering, loyalty, bookings every week) or when you need hardware features the browser cannot offer well.
Where native app projects go wrong
- Building an app before a working website. Search engines index pages, not app screens, so new customers still find you on the web.
- Underestimating upkeep. Each yearly iOS and Android release can require updates, and stores remove apps that fall too far behind.
- Ignoring store review time. A fix is not live until the store approves it and users update.
- No links into the app. Without deep links, emails and ads can only open the home screen.
Related terms
- Hybrid app: one codebase wrapped to run on several platforms.
- Progressive web app: an installable web app with no app store.
- Web app: browser-based software with no install.
- API: how a native app usually fetches its data from a server.