4 ms·
1. Thanks for the feedback! I think that's a really great point. We believe it is also important to optimize for the developer that wonders if a library will wo
by meanJim 9y ago
1. Thanks for the feedback! I think that's a really great point. We believe it is also important to optimize for the developer that wonders if a library will work on everything if they use it.
When we help people, people tend to be confused when a library fails to work on Android and not iOS, and vice versa. We should do a better job about communicating this is a smart way.
2. Our intention was to help the React Native community. In the hypothetical: native.directory could be filled with libraries that aren't compatible with Expo and it would be fine with us. Expo happens to care a lot about React Native and is also a part of this community. There is no disingenuous motive behind our intent.
- RubenSandwich 9y agoYou should still at least list that this is a project from Expo. A tagline like: "From your friends at Expo" would be sufficient. It is important to note this as you include Expo as a compatibility platform on this site when other React native registries, https://js.coach/react-native https://js.coach/react-native & https://github.com/jondot/awesome-react-native https://github.com/jondot/awesome-react-native, do not. Just be honest about why you are doing that.
- meanJim 9y agoGreat point, thanks for the clarification.