Using a React Native framework, such as Expo, is now the recommended way to create new React Native apps You can read more about our official guidance in our latest blogpost: reactnative.dev/blog/2024/06/2…

@reactnative Just gonna drop this here… rn.new

@reactnative I think this is the wrong move. Stop hiding bare react-native on the documentation site. Expo does not support Windows and macOS. We're making a very bad move by not embracing all supported host targets of react-native.

@reactnative i love the outlines for how to be come a framework! could we get some general guidelines on popularity? maybe a rough rule of thumb for stars + npm downloads?

@reactnative Expo need a competition

@reactnative No thx. Been using react native for years without expo limitations and super happy. I’d rather configure more things and be in control rather than deal with expo closed system

@reactnative To me this looks like a step taken to monetize react-native ecosystem. Locking building and publishing behind a paywall in the future maybe ?

@reactnative Why not CLI ?

@reactnative Well deserved recommendation, @expo for president

@reactnative Creating my first eas build right now!

@reactnative Perhaps the real question is why isn't CLI the recommended way?

@reactnative As a React Native developer, i choose bare React Native over expo.

@reactnative 👎🏽

@reactnative I've had no issues delivering a plethora of apps using the CLI. Why should I shift over to Expo? What does it solve?

@reactnative Using a framework on top of a framework?!? ReactNative just needs a universal centralized community/driven set of components and a universal design system UI that can be customized.

@reactnative Huge win for @expo

@reactnative Yeah more dependency to expo ecosystem 🤷🏻‍♂️ worst move IMO

@reactnative At first react native was pain in the ass to work with then expo came to the rescue.

@reactnative Using a React Native framework, such as Expo (we don't have other options), creates a unnecessary vendor lock in. Please, @reactjs and @reactnative stop to force us to use frameworks.

@reactnative While it's great to promote the work expo is doing, I think devs should still use caution before opting to go with a framework. You can achieve a very feature rich app without the need for expo.

@reactnative 😱

@reactnative

@reactnative Expo have been a great tool making development so fun

@reactnative Just started to use @expo yesterday! Didn’t know it’s this much fun 🤩

@reactnative This is so much better!!

@reactnative Trying to delve into working with react native asides working with react on web, hope to find it interesting and fun 😊

@reactnative and what about EAS ?

@reactnative i do love using @expo but the over-simplification in implementing things like deep linking & notifications, leaves devs helpless when errors sustain or migrating between expo versions. deep links work fine on android while sometimes dont on iOS

@reactnative

@reactnative So as a framework, you recommend another framework on top. I think this is probably a bad move. You are creating a dependency & complexity pancake. If your framework is so hard to use that it is best used with another FW on top, then it is probably not a good FW after all.

@reactnative Expo ahhh. NO WAY !

@reactnative Yeah, I'll pass.

@reactnative Deja vu for React.js devs 🫠

@reactnative Windows support could be better tho

@reactnative fair, React Native is a library

@reactnative Yep. Expo is really improved.

@reactnative Good decision