react-native

avigatorIOS is better out of the box than Navigator. The reason for this is that the animations for the transitions are done entirely on the main thread, and so they are not interrupted by frame drops on the JavaScript thread. (Read about why you should probably use Navigator anyways.)" "... As mentioned above, Navigator animations are controlled by the JavaScript thread. Imagine the "push from right" scene transition: each frame, the new scene is moved from the right to left, starting offscreen (let's say at an x-offset of 320) and ultimately settling when the scene sits at an x-offset of 0. Each frame during this transition, the JavaScript thread needs to send a new x-offset to the main thread. If the JavaScript thread is locked up, it cannot do this and so no update occurs on that frame and the animation stutters." https://facebook.github.io/react-native/docs/navigator-compa... Regarding the native-styled and higher-performing NavigatorIOS: "Development belongs to open-source community - not used by the React Native team on their apps. A result of this is that there is currently a backlog of unresolved bugs, nobody who uses this has stepped up to take ownership for it yet." Disclaimer: this comment is written by a consultant undergoing high levels of frustration and may have traces of FUD. If React Native works well for you, I would love to hear about it. Edit: I was really hoping to do some good work on the app today. The frustrating problem this time is that the devtools are entirely broken due to a commit made back in September. https://github.com/facebook/react-devtools/issues/229 "I don't know how to fix this. I now remember that this is why we didn't merge that RN pull request originally." UGH. Shoot me.

), then have small wrappers that declaratively specify the data subscriptions you need for each view. If you ever want to swap out your backend, you just need to switch how you're feeding props to your component hierarchy, i.e. with a Backbone mixin, Flux, or Relay. (In fact, the subscription code in React-Meteor is very conceptually similar to how Relay's GraphQL declarations work, but it has the benefit of giving you a working backend about 5 minutes after changing client code, rather than waiting 5 months for people to dig into the GraphQL reference implementation.) For references, see: https://react-in-meteor.readthedocs.org/en/latest/ and https://github.com/elidoran/cosmos-browserify/ It's also very much worth mentioning that with Meteor's first-class support for oplog tailing, you can always just write external microservices (in any language you want) that are kicked off by Meteor and asynchronously make changes to the database. Then all clients will pick up those changes as quickly as their network connections allow. We use this heavily in production with a Kappa Architecture (see: http://radar.oreilly.com/2014/07/questioning-the-lambda-arch... ) feeding a Mongo database that is itself a [read-only] Meteor Collection, giving our users real-time visibility into, well, just about everything. The details merit a separate post, but it's a complete joy to write code for. Cordova is clunky. But there's nothing stopping your React Native app from loading your full client Meteor code into the JavaScriptCore background view, now that React Native polyfills WebSockets ( https://github.com/facebook/react-native/pull/890 )... then you'd just need to test for whether your app is being loaded into React Native. And there you have the best of both worlds: React Native for your view, Meteor for your models and controllers. Oh, and to address the point of "staking the future of your company on a persistent web socket connection between clients and servers scaling in production" - a very valid criticism of Meteor. But how else were you planning on making all your data real-time in the first place? Meteor is invaluable for getting real-time apps to market, and if you use React, it's flexible enough if you ever outgrow Meteor's assumptions. And that's a good problem to have.

tps://github.com/facebook/react-native/blob/master/package... By this: return fileWatcher.getWatchers().then(([watcher]) => !!(watcher.watchProjectInfo && watcher.watchProjectInfo.root));