Going Native: Reusing Code
summary
Company Hive moves a React web app into React Native for smart‑home apps and finds UI components are largely unreusable so the UI is rebuilt natively, while Redux sagas and translations stay shared in a common folder. SVGs are wrapped as React components and mapped per platform. Styling uses styled-components to share CSS-like rules. Hardware work (Bluetooth, push) uses native SDKs but total custom native code is 2–3 lines of native code beyond library glue.
AI-written summary · about
chapters (9)
- 0:00Intro
- 0:37Components
- 1:45Native vs Web
- 2:41Logic Component
- 3:26SVG Components
- 4:36Styling
- 5:40Business Logic
- 6:18Hardware Integration
- 7:31Reusing Components
related talks
25mGoing Native
28mCross-Platform React
47mReact Native code reuse: Architecture that works
01h 01mReact Native: A Better Way to Do Mobile
39mReact Native - Unleash the power of React in your device
07mFrom Native to React Native
41mReact Native - A native love story
01h 13mMigrating to React Native: A long-term retrospective
