SwiftUI vs React Native: why we always choose native

The cross-platform pitch is genuinely attractive: write one codebase, ship to iPhone and Android, pay once. We understand why businesses ask for it. And yet every app we've shipped is native SwiftUI. Here's the reasoning we walk clients through.

Your users can feel the difference

React Native renders through a bridge between JavaScript and the native platform. Most of the time it's fine. But "most of the time" is exactly the problem — the jank shows up in the moments users touch the most: scrolling long lists, opening keyboards, swiping between screens. Native SwiftUI talks directly to the platform, so the app feels like the iPhone itself feels. Users can't articulate why one app feels cheap and another feels right, but they absolutely notice.

The dependency question

A React Native app inherits the npm ecosystem: hundreds of packages, each updating independently, plus the React Native framework itself chasing every iOS release. When Apple ships a new iOS version, native apps mostly just work; cross-platform apps wait for the framework and every bridge library to catch up. For a business app that needs to run reliably for years, fewer moving parts wins.

Operational apps deserve native too

Much of what we build is operational — checklists, audits, inventory, scheduling tools that staff use on iPads all day. These apps live or die on responsiveness and offline reliability. SwiftUI with CoreData gives us offline-first behavior and instant interactions without fighting a JavaScript runtime for resources on a four-year-old iPad in the back of a store.

"But we might want Android later"

The honest answer: most NJ small businesses we work with run their operations on Apple hardware, and a customer-facing Android version — if it's ever needed — is a separate decision you can make with real data later. Paying a permanent performance tax on day one to keep an option open that you may never exercise is a bad trade.

Thinking about an app for your business? Here's what we build and what it costs.