Split expo and expo go about directory HOT 4 CLOSED

Hello @jpudysz, thanks for the feedback. 👍

A bit more on that topic can be found on the Expo doc page about using libraries, but TL/DR:

Any library that is compatible with React Native is compatible with the Expo project when you create a development build. However, it may not be compatible with the Expo Go app.

And this is a reason why "Expo Go" flag exist, and there is no "Expo" flag, since when using development client (which is the recommended workflow for a while), every module which support one, or both, of native platforms will work with Expo. This means that we would need to add "Expo" label to nearly every library (besides some out-of-tree only cases) which is listed in the directory, which we believe would not improve the clarity.

We also believe that nowadays Expo users can simplify the thinking of compatibility to "if this library works with React Native? yes? than it will work with Expo" from a bit more complicated days of eject and managed flow. 😉

from directory.

Got it!

Then, IMO "Expo" metadata should resolve to the "Expo" label, not "Expo Go" 😅

You mentioned that every library compatible with React Native is also compatible with Expo, but it might not be compatible with Expo Go.

If something may not be compatible with a subset of apps, I would use the generic label "Expo" to let the user discover its availability. Otherwise, setting "Expo" metadata to true and presenting it as "Expo Go" might be misleading, even though it’s accurate for dev clients.

from directory.

We have shipped the flag rename, so it now reflect the actual meaning of it a bit clearer, hope this helps with confusion.

Also thank you so much for pointing this out, and an interesting discussion which lead to those changes. 🙏

If there are anything else you see we can improve, feel free to open an another issue!

from directory.

Wow @Simek what a massive PR 🔥 thank you for considering my proposal!

from directory.