56 articles on Architecture for React Native performance
Showing 16 of 56 articles (Page 3 of 3)
Ash Furrow, AJ Robidas, and Michelle Fernandez from Shopify reveal what actually happens when web, Android, and iOS developers learn React Native. Spoiler: their biggest fears weren't the real challenges.
Shopify went all-in on React Native, but quickly learned that sometimes you need to break the rules. Here's when they write native code anyway.
Jamon Holmgren from Infinite Red explains why his team ditched Redux after years of use. The reasons might surprise you—and they're backed by real production experience.
Junius Ang from Traveloka reveals how a 4-person team manages 5 React Native apps plus a hybrid app using a single architectural pattern. Their secret? The District System.
Talha Naqvi from Flipkart reveals how React Native cut their A/B testing cycles in half while serving 100M+ users. The secret? Strategic compromises and custom infrastructure.
Yusuf Zeren from Trendyol reveals how his team built their GO delivery app entirely with React Native—zero custom native modules required. Their secret? Strategic architecture choices that kept things simple.
The React Native team at Facebook just pulled back the curtain on how they decide what to build next. Spoiler: cross-platform consistency isn't their top priority.
Callstack explores the real-world challenges teams face when scaling React and React Native across web, mobile, and desktop platforms. The opportunities? Bigger than you might think.
Gabriel Peal from Airbnb shares why they walked away from React Native after 2 years and 80,000 lines of code. The decision wasn't what you'd expect.
Facebook's React Native team just dropped a major announcement: they're completely rearchitecting the framework. After 5 years of learning what works (and what doesn't), they're rebuilding the internals while k...
David Muzi from Shopify reveals how they solved a tricky problem: giving merchants access to thousands of third-party apps on mobile without requiring any code changes from developers.
Twitch spent a week investigating React Native for their mobile apps. Here's what their Android team discovered about the framework's real-world viability.
UberEats needed a Restaurant Dashboard for 3-party logistics. Their web app couldn't cut it, so they bet on React Native before it was proven at scale.
Jan Monschke and Peter Minarik from SoundCloud took a gamble on five-month-old React Native technology. The result? They shipped a production app in four months instead of the estimated six.
Facebook just dropped React Native for Android, completing the cross-platform puzzle that started with iOS earlier in 2015. Their first test? Building a production app used by millions of advertisers.
Facebook reveals why React Native emerged from a simple realization: the principles that made React successful on web could transform mobile development. This 2015 post captures the pivotal moment when declarat...