react-native

At this point, I'm quite satisfied with React and use it for most of my new JavaScript UIs. A few potential improvements that come to mind: 1. More strictness in terms of what is and is not valid JSX. Just today I was working on a React Native app that compiled for iOS but not Android. The issue ended up being a stray semicolon, leading to syntactically incorrect code that allowed for a valid iOS build anyway. I would expect it to fail regardless of environment. The error was also very cryptic although this probably has more to do with React Native than React [1]. 2. More proactive warnings at runtime for development builds. React does a great job at telling me what I'm doing wrong; I'd also like it to tell me what I could be doing better. Some ideas are cyclomatic complexity warnings to detect when there is too much branching logic in a

Related: has anyone published an Android app with ClojureScript and React Native? How much did the fact, that React Native for Android is incompatible with 3rd-party 64-bit libraries[1] affect the development? [1] https://github.com/facebook/react-native/issues/2814

* Mentioned in another comment, but generally the performance of animations was poor with mixed in with any other kind of UI rendering - particularly on older phones (when we prototyped iOS we really only focused on the latest two generations of iPhones). * This can be worked around by deferring work when doing transitions/animations based on user interaction but at the time we only had a single Android Engineer (myself) and I felt it would be an overly large hurdle to cross. The team is however still interested in trying again some point in the future now that we have more time for it. * The minimum version we support is API level 16 which is quite old and we may eventually bump that to 17. * We have not evaluated any native-ish alternatives mostly due to bandwidth but also because the goal is to re-use our stores/business logic from th

There's a linked issue in React Native regarding 64-bit: https://github.com/facebook/react-native/issues/2814. In short, you can't use 64-bit dependencies.

FlatList was absolutely the way to go here. In fact, we initially built the list in question when ListView was the only option. During development, FlatList was made available as an experimental component. It made a huge difference switching over to it. The optimisation we needed to do was to use onViewableItemsChanged to toggle the visibility of images. We found that otherwise it wasn't properly emptying the memory of Android devices, and it was easy to crash older devices. After implementing that, we got silky smooth 60fps everywhere. The only issue was there was a bug in RN core. We submitted a PR which was finally accepted about 6 months later: https://github.com/facebook/react-native/issues/16612#event-...

I'm not referring to technical support questions, I'm referring to actual issues with verifiable repros which works everywhere else (inc. their debugger). They dismiss issues with core functionality like their W3C fetch API not being able to maintain long-running HTTP connections which breaks solutions relying on them like SSE [1]. They originally closed it making it known they have no intentions on ever fixing it and have since locked it preventing anyone else from being able to comment on it either. RN enables a fast development model but you'll continually skate into an open mine field of issues where you'll end up wasting time on putting out fires and diagnosing issues only to discover they're known issues they have no intentions of fixing so you'll be spending time on implementing workarounds mitigating broken UX experiences in your

There's a long tail of PRs to go through and review, and the ones we review may take a while to get to a point where they are accepted, but saying PRs are never accepted isn't quite accurate: https://github.com/facebook/react-native/pulls?utf8=%E2%9C%9...

Will React Native finally support exchanging BINARY data (ArrayBuffer, TypedArray) across the bridge? Thus far I have to send binary data as base64 encoded strings! See react-native-fetch-blob for an example, when I read a file. Current state: Example, issue: https://github.com/facebook/react-native/issues/1424 (closed but not solved, quote: "We are trying to keep issues focused on bugs and this is more of a feature request") Documentation for native modules, which kinds of data can be sent back to Javascript: https://facebook.github.io/react-native/docs/native-modules-... (here the iOS docs, but it's the exact same for Android/Java)

My problem with React Native is lack of proper ES6 support on Android. The issues are closed on GitHub instead of being addressed. See https://github.com/facebook/react-native/issues/11232

I understand what you are saying, since I too am upset about many issues being closed without being fixed. I come across them when doing searches for various problems with RN. It's the same with Flow, the Javascript type checker, only that there it seems like nobody from the dev team even cares about the Github repo and the huge list of open issues (hey, at least they don't close them all automatically by bot). On the other hand, the commit history seems pretty active - and that's an understatement: https://github.com/facebook/react-native/commits/master (same for Flow) I think the commit history says more than (auto-)closed issues. They may not share our priorities but they keep working on the project pretty actively.

Actually now React Native uses the MIT license, this was changed in February: https://github.com/facebook/react-native/commit/26684cf3adf4...

React Native has been updated to MIT too: https://github.com/facebook/react-native/blob/master/LICENSE

The left-pad debacle was a registry issue but the current issue is an npm client issue. In my experience, NPM 5 client versions have been shaky and unreliable, and there are problems with popular ecosystems like react-native [0]. I always roll back to npm 4, even on node 9. [0] https://github.com/facebook/react-native/issues/14209