awesome-react-native

hat are problematic in my eyes: - react-native-swiper[1]. Completely custom JS implementation with a "iOS"y look. 8k stars - react-native-gifted-chat[2]. Large completely custom JS implementation of chat UI. 8k stars - react-native-slider[3]: A pure JS implementation of a slider. 1k stars > - React Native you most certainly do get accessibility. My point wasn't that it can't be done, but that it requires significantly more work that, let's face it, most developers will not do. With native UI you get a lot more for free which results in a better user experience for everyone. See https://news.ycombinator.com/item?id=20709259 > - Running a JS VM isn't that bad, but it is a tradeoff. Imo it's completely worth it to prevent having to learn X different languages for each platform. I agree it's a tradeoff and to be fair I don't have more than a hunch that running a JS VM is bad for energy and resource usage. The tradeoff is distinctively on the user's expense in favour of the developers. As developers shouldn't we be making tradeoffs that benefit our users instead? > - The app size evens out, but yes the minimal is higher. However many apps are much larger than 20MB, it's better than other cross platform solutions Yes many native apps do grow quite large too, my point is the default. The most basic RN, but especially Flutter, app is much larger than the native counterpart. Again a distinct tradeoff on the user's experience in favour of the developer. 0: https://github.com/jondot/awesome-react-native#components 1: https://github.com/leecade/react-native-swiper 2: https://github.com/FaridSafi/react-native-gifted-chat 3: https://github.com/jeanregisser/react-native-slider

, and not implementing their own design/UI (which most do), that look and feel can break between OS upgrades and feel out of place, and, * often don't distinguish between platforms (i.e. the developer won't bother implementing the look and feel for Android, where the component is entirely compatible). [1] - https://github.com/jondot/awesome-react-native

tool to do some initial playing around with standard React for the web first to give yourself an understanding of how to use React before moving on to React Native. There's also a "Create-React-Native-App" tool that can help with spinning up a simple RN project. [0] http://www.reactnativeexpress.com/ [1] https://github.com/jondot/awesome-react-native [2] https://github.com/markerikson/react-redux-links [3] http://blog.isquaredsoftware.com/2017/02/presentation-react-... [4] https://www.reactiflux.com

nguages that run on JavascriptCore are allowed to be pushed to market. - You can't know what the future holds. I was part of the Ruby community at the start, then Node, then Go. I was hard core into .NET, and before that Java. I saw platforms and technologies rise and fall, and was surprised over and over. I was much into Silverlight, a technology that Microsoft wanted to take over native development on the Web. Guess what happened to Silverlight? THAT was very nasty. We all know how that feels, but that's nothing to attribute just to React Native. - Regarding patents: I believe we will have alternatives to React Native long-term, with the same properties but we'll still choose React Native :). However I also believe Facebook doesn't use patents in a bad way that the author hints at, as far as we know and as far as we've seen. I also met with core React Native developers, and they're awesome. Practical advise: I'd suggest for the author to meet with the React Native core team.