• Over-the-air (OTA) updates, users needn’t update their apps • Faster product iteration, and even faster bug-fixes (just like web!) • Cross-platform code sharing • Saved costs, same dev owns the feature irrespective on both platforms
to native via Native Modules For moderate computation tasks, use InteractionManager.runAfterInteractions() Make sure traffic on your JS bridge is as smooth as possible
Our implementation: Wrap each react screen in its own activity/ ViewController and let a NativeModule handle navigation Unnecessary initialisation of two ReactActivities/VCs Can we do better?
Our implementation: Wrap each react screen in its own activity/ ViewController and let a NativeModule handle navigation Unnecessary initialisation of two ReactActivities/VCs Enter react-native-navigation by wix Can we do better?
(@myntra.com IDs) for a day or two, and then do percentage rollouts to external users • Support at most last 3 (android) & last 2 (iOS) app versions • Ensure new features are released simultaneously on both platforms
RN • Ideal state: Single React Activity/VC & Single WebView • Divide our bundles into core and feature bundles • OTA diff updates (Sending only what is necessary)
ReactXP by microsoft • A fresh, end to end alternative to REST based implementations (React + Relay + GraphQL) • Ever growing and active community • More companies now use it in prod (Instagram, Airbnb, Amazon, Walmart, Flipkart, to name a few)
dev experience • We are android/ios/web mobile developers • We think react-native and PWAs are the game changing technologies to come out in recent years of mobile evolution