None of this would have been possible without the amazing React Native community. We believe in the community and are still excited to see it mature and innovate for years to come.
Deze collectie tonen
After two years, 220 screens, and 120,000 lines of javascript, we're moving away from React Native at Airbnb. I tried to summarize our experience in a single blog post but that wouldn't do it justice so it turned into five!https://medium.com/airbnb-engineering/react-native-at-airbnb-f95aa460be1c …
-
-
Bedankt, Twitter gebruikt dit om je tijdlijn te verbeteren. Ongedaan makenOngedaan maken
-
-
-
Did you folks consider moving to Xamarin? Lottie runs on there, and I think you might have a much better experience than React Native.
-
How would Xamarin have solved our problems? In particular, the organizational ones and overcome the fact that we have a huge amount of React expertise and infra that we could leverage for RN.
-
Well, you’re moving away from React and going straight native now, right? Or did I miss something in Part 5?
-
We never stopped doing native. React Native was never more than 10-20% of our mobile engineering effort.
Einde van gesprek
Nieuw gesprek -
-
-
I am really curious if you considered
@flutterio -
1) Flutter wasn't an option when we began to consider this in early 2016. 2) We were able to leverage huge amounts of React expertise and existing infra. 3) Many of the challenges were not RN specific and would be the same in flutter.
-
Several of the technological issues are JavaScript specific, though. Wouldn't switching to a type-safe language like Dart help?
-
A few issues, certainly, but there would be new ones such as the fact that we wouldn't be able to leverage our existing React expertise and infra or share code with web.
-
Having done native, Ionic, RN, and Xamarin, I gotta say that having development tools you can’t trust and debugging environments that are PITA to set up and use is a million times scarier than having to maintain two platform codebases.
Einde van gesprek
Nieuw gesprek -
-
-
Question: 100 engineers only for the app frontend?
-
We have had 122 engineers with 10+ commits to Android/iOS/RN in 2018. People often think of Airbnb as seach, booking, payments, and itinerary but it has an enormous featureset for hosts, regions, experiences, and much more.
-
10+ commits, that's a week for me, sometimes a day...
-
Many of these engineers work on mobile in parallel with backend/web/etc. For that reason, it's impossible to have an exact count of mobile engineers. That, or you're just a 10x engineer...
-
as the old saying goes: what one programmer can do in one month, two programmers can do in two months :)
-
In my experience, the more complex your project gets, the more time it takes to bake in new stuff. Although I see your point with 10 commits.
-
If your project lacks conventions and guidelines then "new stuff" will indeed take longer to add. With good conventions (e.g. Rails is great in that respect) you don't have to think about where and how to add code.
-
Agreed. But it doesn't take away the fact that things get trickier as codebase grows. Even with good test coverage.
Einde van gesprek
Nieuw gesprek -
-
-
Reading that blog post was kind of painful because it seems that what you really need is Xamarin. What can we do to help you?
-
Why would Xamarin have solved our problems, especially the organizational ones?
-
One team instead of two, real native apps instead of some kind of Franken-apps that don't perform. Many people don't know that Xamarin produces real native apps and not hybrid.
Einde van gesprek
Nieuw gesprek -
Het laden lijkt wat langer te duren.
Twitter is mogelijk overbelast of ondervindt een tijdelijke onderbreking. Probeer het opnieuw of bekijk de Twitter-status voor meer informatie.