r/iosdev • u/Stycroft • Mar 12 '26
I chose React Native over Swift for my iOS app. 2K downloads later, here's what I wish someone had told me.
When I decided to build a grocery budgeting app, I had a choice: learn Swift and build native, or use React Native (which I already knew) and ship faster. I chose React Native. Here's the honest trade-off report after 3 months and 2K downloads.
Why I didn't go native: Solo dev. Already knew TypeScript. Future Android version. Expo's tooling was too good to pass up.
What's genuinely great on iOS:
Expo Router — file-based routing like Next.js. Adding a screen = adding a file.
OTA updates — bug fixes skip App Store review entirely.
Firestore offline persistence — just works. Users don't notice when they lose connection.
expo-haptics + native animations. Users don't know it's React Native.
What's honestly not great:
~60MB bundle vs ~15-20MB native Swift.
InputAccessoryView needs a bridge. Some iOS interactions aren't first-class.
Cold start ~1.5s. Acceptable, not great.
Performance ceiling. Fine for utility apps, not for animation-heavy apps.
Would I choose Swift if starting over? For this app — no. DX savings are too significant solo. For WidgetKit, ShareExtension, or heavy native stuff, I'd reconsider.
Stats: 2K downloads, 95% crash-free, fully offline, TestFlight in ~15 min.
https://apps.apple.com/app/grocerybudget-shopping-list/id6749287517
Am I leaving performance on the table, or is "good enough" good enough for utility apps?