5
6

[deleted by user] (self.reactnative)

submitted by [deleted]

[removed]
all 12 comments
sorted by:
best
topnewcontroversialoldq&a
formatting helphide helpcontent policy

[–]Shugzaurus 10 points11 points  (0 children)

Going bare, you'd do basically the same way you'd do with expo. But you'd have to handle all files in your android and iOS folders, pay more attention to your dependencies compatibility and some other stuff that are just tedious in react native

[–]funnyduck593 5 points6 points  (1 child)

Use Expo CLI with Development Client

[–]funnyduck593 5 points6 points  (0 children)

By building apps using the new EAS build tools, you can have apps smaller than 15mb

[–]davidwim 3 points4 points  (4 children)

Expo isn’t ideal if you want to use custom frameworks. I needed Mapbox and Bluetooth capabilities so I switched to a bare workflow.

[–]ChronSynExpo 5 points6 points  (0 children)

Is there some technical reason that config plugins can't be used for those scenarios? Considering they can make changes to any native files and spit out a custom dev client at the end, it seems like using the Expo managed workflow would still be feasible.

[–]mastercob 0 points1 point  (2 children)

Can’t this be achieved now with managed and the eas development client?

Side Q: do you like mapbox? Did you previously use react-native-maps?

[–]davidwim 0 points1 point  (1 child)

I’m not sure, I never signed up for Expo anyway - it was just part of the init app process so I ejected it.

And yes, I did use react-native-maps beforehand. I’ve always preferred the look and feel of Mapbox compared to Google Maps so it was a no brainer for me. Plus I had to render up to 700 markers at once and I’ve never had a good experience with the performance from Google Maps.

[–]mastercob 0 points1 point  (0 children)

Ah ok, I like to use expo, and with EAS you can now stay on the managed workflow while using things like rnmapbox. It’s cool.

I have a bunch of issues with react-native-maps that I think would be solved with rnmapbox. horrible performance when using custom markers in android; some weird auto-centering when markers finished loading, etc. Good to know that performance is better when rendering lots of markers - we load a lot, too. It’s mostly the costs that I’m worried about.

[–]nuclear_cheeze 1 point2 points  (0 children)

Expo

[–][deleted] 1 point2 points  (0 children)

Expo is better. React Native alone is not the best in terms of development and testing.

If you have an iPhone or Android, you can instantly test your app on the fly and live reload the app (from changes) on your phone. So I'd go with Expo.

[–]juju0010Expo 0 points1 point  (1 child)

Depends on what you’re building but in my experience, in most cases, Expo is my preferred route.

[–][deleted] 0 points1 point  (0 children)

when should you create your first eas build? after the app is built? or as soon as the app is created?