Going Native
summary
Recounts a pragmatic migration: web UI components mostly don’t survive, styling is partially reusable via styled-components and shared design tokens, business logic is fully reusable — Redux and redux-saga run unchanged in a JS runtime, native features use existing libraries for camera and Bluetooth, and a custom sync tool (soon replaced by a monorepo) handles shared code. Reports a 15,000-user trial, RAM bundling gives native-like startup performance, and only two or three in-house native modules are necessary while the rest comes from the React Native ecosystem.
AI-written summary · about
chapters (9)
- 0:00Start
- 0:42What we do at Hive
- 6:52React native rendering
- 8:47Mapping components
- 9:32Cross platform components
- 10:37Logic components - conditional feature
- 11:07Props components - SVGS
- 12:36React Native styles
- 13:31Styled components
related talks
09mGoing Native: Reusing Code
28mCross-Platform React
01h 13mMigrating to React Native: A long-term retrospective
29mA practical approach to building truly native cross-platform applications at scale
41mReact Native - A native love story
01h 01mReact Native: A Better Way to Do Mobile
35mBridging the Gap: How to use React Native in existing large native code bases
07mFrom Native to React Native