Organizing Code for Cross-Platform Web and Mobile Development
summary
Claims 70% business logic code reuse while keeping platform-specific UI, and organizes modules as a shared business-logic layer plus web and react-native folders with a package.json per target. Uses a babel target alias so imports resolve to web or native builds, demos a telnum input implemented once for formatting and twice for rendering, explains native wrappers that inject UUID references to route singleton native-module calls, and ships a react native toolkit and macros to remove boilerplate.
AI-written summary · about
chapters (16)
- 0:00Cross-platform development intro
- 1:06Code organization importance
- 5:42Talk structure
- 6:06Writing apps three times
- 8:15Merging web and mobile
- 9:19Shared business logic
- 11:45Shared folders for code
- 13:31Cross-platform component
- 16:21Web component implementation
- 17:44Publishing as node modules
- 18:49Native integration strategies
- 21:41Native wrapper details
- 23:27Routing to components
- 27:03Reducing boilerplate
- 28:28Key takeaways
- 29:10Q&A
related talks
47mReact Native code reuse: Architecture that works
21mBuilding Cross-Platform Component Libraries for Web and Native with React
59mOne Codebase to Rule Them All - Using React Native Everywhere
36mThe sorcery of building a cross platform Design System architecture
35mReact Native & Rails, A Single Codebase for Web & Mobile
50mBuilding Cross Platform Native Mobile Apps using React Native
34mMonorepo: React Web & React Native
30mJesse Weigel - One Codebase to Rule Them All - Using React Native Everywhere
