Due to a variety of technical and organizational issues, we will be sunsetting React Native and putting all of our efforts into making…
Overview
The article discusses Airbnb's decision to sunset React Native due to various technical and organizational challenges, opting to refocus efforts on native development. It reflects on the experiences with React Native, highlighting both the positive aspects and the difficulties encountered during its implementation.
What You'll Learn
1
How to evaluate the effectiveness of React Native in your organization
2
Why transitioning from React Native to native development may benefit your projects
3
When to consider sunsetting a technology in favor of native solutions
Key Questions Answered
What were the main reasons for Airbnb's decision to sunset React Native?
Airbnb decided to sunset React Native due to an inability to meet original goals, compounded by technical and organizational challenges. The transition plan includes halting new React Native features and focusing on native development for better performance and quality.
What was the overall sentiment of engineers who worked with React Native at Airbnb?
Among engineers who used React Native, 60% described their experience as amazing, while 63% would choose React Native again if given the chance. This indicates a generally positive sentiment despite the challenges faced.
How did React Native affect the speed and quality of development at Airbnb?
While React Native allowed for rapid development when functioning well, various technical and organizational issues led to frustrations and delays. The article notes that the developer experience was mixed, with improvements in some areas but significant challenges in others.
What is the sunset plan for React Native at Airbnb?
Airbnb's sunset plan involves creating a transition strategy, halting new features, and moving high-traffic screens to native by the end of the year. Support for React Native will continue through 2018, with a ramp down in 2019.
Key Statistics & Figures
Engineer sentiment
60%
60% of engineers described their experience with React Native as amazing.
Reconsideration rate
63%
63% of engineers would have chosen React Native again given the chance.
Code contribution
80,000 lines
Engineers wrote 80,000 lines of product code across 220 screens.
Key Actionable Insights
1Evaluate the specific needs of your projects before adopting React Native.Understanding your team's composition and existing app requirements can help determine if React Native is the right fit, as Airbnb's experience shows that hybrid solutions can introduce complexities.
2Consider the long-term implications of using a hybrid framework like React Native.Airbnb's challenges highlight that while initial speed may be appealing, the potential for technical debt and organizational friction should be carefully weighed.
3Engage with the community when transitioning away from a technology.Airbnb's decision to migrate some React Native work to the react-native-community demonstrates the importance of supporting open source and maintaining community ties during transitions.
Common Pitfalls
1
Failing to adequately assess the technical and organizational fit of React Native for your specific context.
Airbnb's experience illustrates that what works for one organization may not work for another, emphasizing the need for thorough evaluation before adopting new technologies.