r/reactnative • u/claudine_26 • Dec 23 '24
Why use Expo for React Native Development
Curious about Expo and how it can level up your React Native development? A colleague of mine recently wrote an article about what it is, its benefits, and how to get started. He compares Expo CLI with React Native CLI, and describes how to build a React Native Expo app. If you're interested to read it, here's the link :)
19
u/BuggyBagley Dec 23 '24
Expo does save a bunch of time especially managing certs and permissions. All those expo plugins are pretty neat too. But what has worked for me is to use expo for all the crazy certs and keys management and just fucking learn swift and java and build some custom native modules to do whatever without being limited by JS or expo.
17
u/AdMajor6687 Dec 23 '24
This is actually how React Native development was supposed to be done from the beginning. I believe this was the original vision - for React Native CLI to be a convenient way to bootstrap Android and iOS apps, for JS (React) to be a convenient way to write UI and logic for both simultaneously, and for the native projects to allow us to build whatever functionality isn't readily available.
Unfortunately, most RN developers think of React Native as a hack that allows you to get around having to deal with anything native. That's where all the problems start. Mobile developers should always understand and be comfortable with the platforms they work with, not run from it.
You sir are a true mobile dev.
5
Dec 24 '24
Try setting up RN in android studio, it's a mess, I tried 5 days ago failed. Expo is easy to setup, I built 10 apps never came across a scenario where I needed to tweak native things
1
4
u/crux153 Dec 23 '24
Continuous Native Generation (CNG) https://expo.dev/blog/what-is-continuous-native-generation
2
u/harunpasha Dec 23 '24
It is crazy... I don't use build stuff (EAS) that much, but it is growing day by day and saves you so much time. You don't have to touch native code at all. It bundles everything(keys, credential files, permissions, etc.) for you. Now you can even code your iOS widget with Expo (it is not official yet).
2
u/Sufficient_Ant_3008 Dec 25 '24
If you need the WebRTC lib it's broken currently from what I've seen. The best reason to not use Expo is if you need to leverage a native feature (playing audio on lock screen). You can make this feature in Expo but it's a workaround at best or you're going to use an RN lib. However, Expo 52 doesn't support legacy stuff and the last thing I want is a --legacy-peer-deps on my npm command.
If you need an app store presence, a great set of tools, and 95% of what you would need to build an app, then Expo is going to be the best route. Even if you are missing some "core" features, forgoing convoluted, "bleeding edge" features will most likely save your app and project as a whole.
I recently ran across a guy making a bare bones app, it's been in development for 2 years and still hitches on the home screen. With Expo you're going to lose out on that "pure speed feeling"; however 'member, our eyes can't see 8k, and I believe anything over 500ms is unpleasing, so if your rendering is a seeing a 400ms load time and 200mb memory usage when you would have a 200ms load with 100mb memory usage then you'll waste your time trying to optimize without Expo. To be fair that guy is making an app that needs optimal responsiveness; however, I would have taken two years on two native apps myself.
Just Get in the Expo Box and stay in it for 2025 my friends!

2
u/ajnozari Dec 23 '24
Just started a new RN Project. Decided to reach for expo first to see how it’s matured. Yes I use prebuild and local builds, but everything has become so much easier, it really has matured and I went from blank template to starting to code the meat of the app in less than a day. Even adding in theming and such didn’t take long thanks to expo router being based off react navigation and react-native-paper having a theme adapter.
1
1
1
u/Always-Bob Dec 24 '24
Expo really is great but I would say research your features before hand. I wanted to use a local database and later found out that MMKV was not supported in expo and we have to do a pre-build before running it. Similarly there was another lib that needed a pre-build, at this point I thought doing bare bones RN without expo.
1
u/Regular_Wash_4378 Jan 01 '25
I’ve been using Launchtoday for my mobile app projects, and it’s been a game-changer. The pre-built features and integrations have saved me so much time, allowing me to focus on the unique aspects of my app. If you’re diving into React Native development, I highly recommend checking it out. It’s perfect for getting your app idea off the ground quickly!
1
u/f4z3k4s_scriptide Jul 22 '25
I also wrote a pretty comprehensive blog post on the topic not so long ago: https://scriptide.tech/blog/should-you-use-expo-for-react-native
1
u/thatweirdkid2017 Dec 24 '24
Do not try expo if your plan is to take over native side of it. Expo is highly opinionated. I still find a bare workflow still better than expo.
-11
Dec 23 '24
i dont know any reason to actually use expo.
the whole argument is that there is no reason not to use it, but my reason is that you dont need it
6
u/tcoff91 Dec 23 '24
Continuous native generation of native projects is amazing. Also their libraries are really good.
0
7
Dec 23 '24
[removed] — view removed comment
13
1
1
u/alotmorealots Feb 23 '25
now i have to check over 70 dependencies by hand and see why the build fails
Made me wince just reading that and knowing there's an automated alternative lol
1
Mar 04 '25
[removed] — view removed comment
1
u/alotmorealots Mar 04 '25
Oh, I was just referring to your comment on how different things would have been if you had used Expo:
while expo updates all their packages accordingly and provides rigorous changelogs for each of them in the same place.
8
u/apppai Dec 23 '24
expo is awesome much better dx when you develop something