Sharing Code Between React and React Native: What Not to Share - Ben Ellerby





The interactive transcript could not be loaded.


Rating is available when the video has been rented.
This feature is not available right now. Please try again later.
Published on May 3, 2019

Talk recording from React Amsterdam 2019 Conference  

Check out the latest React Summit Amsterdam news – https://reactsummit.com

See other React conferences by GitNation
React Day Berlin – https://reactday.berlin
React Advanced London – https://reactadvanced.com

# Sharing Code Between React and React-Native: What Not to Share
# React Native Track

React and React Native allow a "learn once, write anywhere" paradigm. This is great because one tech team can build both your web app and native mobile experience. The problem is developers hate writing things twice. There have been a couple of efforts to build a unifying technology to write an application once and have it work on both web and native. Yet this is not always the best approach. There is value in only sharing your business and state logic; keeping your render code separate.

In this talk, Ben Elerby gives real examples from his work with MADE.COM, migrating their web and mobile application to React and React-Native with code sharing as a primary objective.

Subscribe to our channel to see more React (Native) talks: https://www.youtube.com/channel/UCsFr...


When autoplay is enabled, a suggested video will automatically play next.

Up next

to add this to Watch Later

Add to

Loading playlists...