Crossing Paths of React And React Native Ecosystems

The guests trace React Native’s roots to React’s focus on the view layer and the separation of React core from its renderers. That architecture let React Native render native views, while React DOM continued to render for browsers. They describe shared components, hooks, state logic, and API access as a bridge across platforms.

Jack says his React Native work was smooth until he added an ONNX Runtime driver for local AI, where he ran into more friction. He praises Expo’s built-in capabilities, including camera features, and says it is a strong path for apps that stay within its supported ecosystem. The guests compare Expo’s accepted role in React Native with the more contentious choice of frameworks in web React.

The guests describe React Native developers as highly engaged, partly because early tooling required hands-on troubleshooting and companies built libraries and support. Jack contrasts that with web development’s more polished starter experience, where developers may expect things to work immediately. Simon says building and shipping a mobile app can feel especially rewarding because it integrates with personal device features such as the camera and microphone.

Simon argues React Native suits many projects when teams value shared code and faster delivery, while acknowledging that other frameworks fit some needs better. The discussion covers experiments in bringing React concepts across platforms, including server components, React Native Skia, and shared component libraries. They also note that web and native still have different renderers, navigation patterns, and platform requirements.

The guests discuss debugging React Native build failures involving Gradle, Swift, Xcode, Node versions, and dependency changes. Simon describes dependency bit rot and says Xcode changes can break workshops that previously worked. They suggest that familiarity helps developers recognize recurring issues, such as provisioning profile problems, while Expo reduces some but not all friction.