Do these 3 things before closing this tab:
1Scan for outdated or missing drivers - takes under a minute2Repair Windows errors before they cause bigger problems3Fix the driver behind crashes, sound loss and screen glitchesBytes #150’s January 5, 2023 take on React Native was cautiously optimistic: React skills could carry over, and Expo and Hermes looked promising, but platform-specific work, performance concerns, library maintenance, and routing frustrations remained. The newsletter offered a snapshot ahead of React Native 0.71—not a measured comparison or a verdict on React Native today.
What Bytes #150 was asking
Published on January 5, 2023, Bytes #150 – React Native vibe check asked whether React Native’s cross-platform trade-offs were improving enough to make it worth trying. The issue described the framework as having been around for “almost 8 years,” a rounded historical description rather than a precise launch-date calculation.
As an Amazon Associate I earn from qualifying purchases.
Its framing captured a familiar tension: developers may get to use React, but the app still has to meet the expectations of people using iOS and Android. The newsletter attributed to former React Core Team manager Tom Occhino the description of React Native as “one of the most controversial technologies of all time.” Bytes reported the quote indirectly; the issue did not provide a primary transcript.
Free tools Windows power users keep installed
One-click scans. No signup required.
What the newsletter criticized
Performance and user experience
Bytes said React Native apps can feel slower, jankier, or less reliable than native iOS and Android apps. It suggested that shipping too much JavaScript and putting developer experience ahead of user experience could contribute. These were the issue’s assessments, not conclusions backed by benchmarks: it supplied no quantified performance results or systematic comparison.
#1 Best Overall
Libraries and routing
The issue also pointed to the quality and maintenance of third-party libraries as ecosystem challenges. It described routing as a longstanding frustration for both React developers adapting to mobile and mobile developers learning React. Those observations identify areas a team might investigate; they do not establish how every project or library performs.
Why Bytes saw reasons for optimism
The positive signs were specific to the early-2023 release context. Bytes highlighted Expo 47’s file-based routing and concurrent features, React Native 0.70 making Hermes the default, and first-class TypeScript support expected in the then-upcoming React Native 0.71 release. These are historical points from the newsletter, not current version or upgrade guidance.
Rank #2
The broader promise was that React knowledge could transfer across platforms. Bytes preferred “learn once, write anywhere” to “write once, run anywhere”: the former leaves room for platform-specific implementation instead of implying that one codebase eliminates all iOS and Android differences.
How to read its adoption signal
Bytes named Discord, Coinbase, and Shopify as popular apps that had migrated to React Native and characterized their reviews positively. The issue supplied no links or case-study details for that claim, so it is best treated as Bytes’ report—not as an independently verified endorsement or evidence that React Native suits every app.
Rank #3
What this vibe check can—and cannot—tell you
The newsletter is useful as a record of the trade-offs its writers saw in January 2023. It does not provide a framework shootout, adoption-rate data, market-size figures, or measured performance statistics. Its concerns and promising developments should not be mistaken for a current evaluation.
For a project decision, the questions raised by the issue remain practical decision axes rather than a ready-made winner:
Rank #4
- User-perceived performance: What responsiveness and reliability does the app need, and how will the team test those qualities?
- Dependencies: Can the team find and maintain suitable libraries for both iOS and Android?
- Routing and workflow: Does the routing approach fit the product, and is the team comfortable with the development experience?
- Platform-specific work: How much iOS- or Android-specific code and behavior can the project accept?
Bytes #150’s central point was not that React Native removes platform differences. It was that React knowledge can travel while meaningful platform work remains. The release references explain why the newsletter felt more hopeful in early 2023; they do not establish how the framework stands today.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
