Panel Discussion
summary
Discussion names concrete pain points and concrete bets: list performance stalls on phones with 10,000 contacts and teams expect JSI to cut bridge overhead; agencies report 25–35% of time on open source while some companies follow an 80/20 product-to-community split; Expo intentionally tracks upstream React Native and reduces forks, but multiple SDK versions require small patches; RNTester exists as a source-of-truth for component behaviors; Fabric/new architecture needs years of migration and library updates, with optimistic timelines around 18 months–2 years for wider maturation.
AI-written summary · about
chapters (13)
- 0:00Introduction of panelists
- 1:04Web vs native app debate
- 4:55Sound issues resolved
- 5:17React Native improvements needed
- 9:07Server-driven UI in React Native
- 12:42Open source contributions balance
- 19:25Expo's growing role in React Native
- 23:04Expo vs React Native divergence
- 27:17React Native lessons from Flutter
- 30:09Hidden React Native gems
- 31:52Fabric architecture adoption
- 36:45Future of React Native
- 42:29Closing remarks and thanks
