Navigating React Native Navigation
summary
A prototype mobile app for Major League Soccer implements about nine features in six weeks and forces a hard look at navigation. The evaluation surveys roughly ~137 solutions and compares three actual candidates: native navigation (native Swift setup, CocoaPods pain, smooth animations, early beta), react navigation (JS easy install, occasional transition lag), and react router v4 (chosen for cross‑platform flexibility); the working prototype succeeds and routing decisions hinge on platform targets and animation tradeoffs.
AI-written summary · about
chapters (40)
- 0:00Introduction
- 0:31Welcome
- 1:14Backstory
- 1:33Major League Soccer
- 1:57Facebook Messenger
- 2:16Reduce duplication
- 2:44MLS love React
- 3:00Try it on mobile
- 3:27Can I do everything on mobile
- 3:43We were really impressed with
- 4:01Our biggest successes
- 4:20Bridging
- 7:10Consistency
- 7:20Flexibility
- 7:42Developer Experience
- 8:07Strong Community
- 8:35Stable
- 8:55Deep Linking
- 9:33Native Navigation
- 13:10Custom Navigation
- 13:44React Native Navigation
- 16:33React Native Navigation Demo
- 17:17Crossplatform
- 17:44WebNative
- 18:12Screen
- 18:51Higherorder navigation
- 19:03Integrating other navigation solutions
- 19:29Screen transitions lag
- 20:10Long Titles
- 20:41Navigation Options
- 21:19React Router
- 21:39React Router Pros
- 22:03React Router Cons
- 22:27React Router Crossplatform
- 23:01React Router Components
- 23:56Cons
- 24:26Android Back Support
- 26:38Example Apps repo
- 27:08Questions
- 28:08Experimental
related talks
45mMobile navigation
07mFrom Native to React Native
31mFrom React to Native
27mNative Navigation for Every Platform
31mUsing React Native to ship fast and navigate performance improvements
26mComponent based Navigation in React Native
31mRewriting a Large Hybrid App with React Native
13mIntegrating React Native with Native Infrastructure