Native: the platform's own language and tools
Native development means Swift (or Objective-C) with Xcode for iOS, and Kotlin (or Java) with Android Studio for Android — two entirely separate codebases, each using the platform vendor's own tools and APIs directly.
The case for native
- First access to new OS features and APIs, often before cross-platform frameworks catch up
- Best possible performance, since there's no bridging layer between your code and the platform
- UI that matches platform conventions exactly, since you're using the platform's own UI toolkit
The tradeoff is real duplication: essentially two apps, two codebases, two teams (or one team context-switching), and every feature built twice.
Cross-platform: one codebase, both platforms
React Native, Flutter, and similar frameworks let you write one codebase that compiles or renders to both iOS and Android.
// A React Native component — renders on both platforms
function Greeting() {
return (
<View>
<Text>Hello, mobile world</Text>
</View>
)
}React Native renders using actual native UI components under the hood (not a webview), while Flutter draws its own UI with its own rendering engine — a subtle but real difference in how closely the app matches native platform look and feel by default.
The genuine tradeoffs
Cross-platform frameworks mean one team, one codebase, and faster shipping for most features — a real and often decisive advantage for a small team or a startup validating an idea. But you occasionally hit platform-specific quirks that require dropping into native code anyway (a "bridge" or "native module"), and adoption of brand-new OS features usually lags behind pure native by weeks or months.
There's no universally correct answer. A small team building a fairly standard app (forms, lists, API calls) is usually well served by cross-platform. An app pushing hard on platform-specific capabilities — deep camera control, complex animations tied to OS gestures, AR — often needs native, at least for that specific feature, even inside an otherwise cross-platform app.
Progressive Web Apps: a third option, with limits
A PWA is a website that can be "installed" and behave somewhat like an app — offline support, a home screen icon, push notifications on some platforms. It avoids app store review entirely, but has real limits: iOS historically restricts PWA capabilities more than Android, and neither platform gives a PWA full access to native APIs the way a real app gets.
Comments