Assuming the person you're talking about was me, I'm curious what it was I said that made me seem less enthusiastic? I always try to be as honest as possible in my interviews, and I don't think my enthusiasm has changed much over the last year or two, though I certainly have learned a lot!
I don't think Airbnb has ever been "completely going all-in on React Native" or "completely dropping React Native", but people always seem to want it to be one or the other. The truth is it's almost always something in the middle.
This just isn't true. Airbnb is actively using React Native a lot and has not "stopped using it seriously". I'm not sure where you got this impression. Some people responding to this are mentioning the transition of the potential native-navigation library to react-community. This is a library that we never actually used in production, though the plan was to move off of our internal library to this one shortly after open sourcing it. Priorities shifted internally (to other, more pressing react-native related things that aren't OSS), and we have not yet been able to do that. Since the community really wanted to work on the library despite us not actively maintaining it, transitioning it to react-community seemed like a better thing to do than further fragment the community by having people fork it. I'm still hopeful that we will be able to migrate to it in the future.
Source: I am the tech lead of React Native infrastructure at Airbnb and the primary author of native-navigation.
I'm not sure what you mean by this? The react-native version does nothing but wrap the ios/android libraries (which are CoreAnimation and Canvas based, respectively)
It doesn't yet, but I hope to work in integrating these two very very soon. We have to figure out what this will look like on Android, as the TransitionCoordinator on iOS doesn't have an exact equivalent on Android.
Various flows in the Airbnb app are built with React Native. Our recently launched "Experiences" platform is built mostly with React Native, and there are many flows in the app that are built with React Native. Overall it's probably about 10-20% of the app right now. The decision to use or not use React Native for a new feature is a function of what the team building the feature is familiar with, and whether or not we think we can deliver a good user experience with the technology or not. The answers to those questions are quickly evolving though as we build up more infrastructure around React Native, and as the familiarity with the platform grows.
> What has been your experience?
Generally positive, but the difficulty of integrating React Native into an existing mobile app with large existing native code bases should not be understated. It's not plug and play. I'm giving a talk about this in detail at React Conf in March. Make sure to check it out!
> If you were starting a mobile company now, would you start with RN ?
Yes.
Keep in mind that I was the main proponent of React Native being experimented with and adopted at Airbnb. As a result, I have some bias and other people at Airbnb might have different feelings / experiences.
Great question. Right now playing the animation with the imperative API in React Native will be driven entirely on the main thread, but the declarative API with `Animated` will not be (yet).
I'm very interested in building the proper hooks natively to allow for usage with `useNativeDriver: true`. We are perfectly situated for this too, considering the author of the iOS side was also the engineer who introduced offloaded animations to React Native on the iOS side!
(Source: I made the Lottie RN bindings, and work on RN at Airbnb)
That's a fair point... but I guess the primary point I was making was that it's important for the founders themselves to understand this dynamic. Their interests and the investors' interests are not perfectly aligned.
Thanks for the feedback, and for trying it out. Was it clear that that page was skippable, and that the years experience were optional?
I will take another look at the signup process. While I want it to be quick, the onboarding process is important for people to customize their experience and find who they know, etc. Definitely needs to be quick and easy though.
Tech.pro is a niche social network for people in Tech, with a focus on content discovery and sharing. It's designed with blogging in mind, while also allowing users to share links, images, Q&A, micro-posts, etc.
Our main feed (the home page) is driven by a combination of the people you follow (your network) as well as the tags you follow (your interests). We've been working hard to make the platform work well for the broad range of interests that someone in the tech industry might have.
Inspiration for the site has come from many sites and communities that exist today including HN, Reddit, Facebook, Twitter, etc. but take unique aspects of each to make the best possible experience.
I'm eager to get any sort of feedback from the HN crowd. AMA
Funny... I actually created some store mixins to do the exact same thing.
I've done it slightly different than you... rather than using `mergeDeep` in `this.setState`, I created some other methods such as `this.setStateAtPath(path, value)` and `this.mergeState` (the latter would use `mergeDeep`)
This looks to be a well-put-together implementation of flux. I recently looked over around 20 or so flux libraries to use for a react app I had started, and found only a couple that I liked. I would put this one near the top, but the one I ended up choosing has been great, but no one seems to know about it!
> Building a vehicle to carry sufficient fuel and supplies for the trip to Mars is not especially technically challenging, when compared to the design of an earth-entry vehicle. Earth orbit rendezvous allows for the assembly of massive (though expensive) space vehicles such as the ISS.
Of course, they do have to land on mars, don't they? Isn't this roughly similar (and thus similarly as challenging) as earth re-entry?
I don't think Airbnb has ever been "completely going all-in on React Native" or "completely dropping React Native", but people always seem to want it to be one or the other. The truth is it's almost always something in the middle.