React Native, honestly: a 2026 buyer's guide for Australian engineering leaders

About 388 Australian companies ship React Native in production today, per TheirStack's directory of live AU mobile estates. None of them are running the framework you remember from 2018. The bridge architecture Airbnb sunset in their well-known engineering post no longer exists in the codebase. It was deprecated in React Native 0.76, defaulted off in 0.79, and permanently removed in 0.82. Hermes V1 became the default JavaScript engine in 0.84 in February 2026. So if your team's mental model of React Native is anchored on the version that broke Airbnb's mobile org, your mental model is seven years stale.

What actually changed

Three things matter from the last 18 months.

First, the New Architecture: Fabric for rendering, TurboModules for native calls, JSI for direct JavaScript-to-native binding, Codegen for type-safe interop. This became default in 0.76 and mandatory in 0.82. Roughly 90% of the major ecosystem libraries (React Navigation 7.2+, Reanimated 3.5.1+, Vision Camera 4+, Expo SDK 52+) autolink against it. The async bridge that Airbnb cited as their first technical complaint is gone.

Second, Hermes V1 in RN 0.84. The new JavaScript engine cuts JS-to-native call latency by roughly 40 times relative to the legacy bridge, and TurboModules deliver a 30 to 43% cold-start improvement on typical apps (vendor figures; treat them as upper-bound numbers, but the direction is right).

Third, React 19 landed in RN 0.78 in February 2025 with no breaking changes for React Native consumers. The web and mobile React teams are sharing one runtime. Expo SDK 55 (April 2026) ships RN 0.83 with Expo Router as the default for new projects, which gives you file-based routing across iOS, Android and web from a single source tree.

What is true about performance now

Cross-source benchmarking is messy and most numbers come from second-tier publishers. The strongest cross-validated pattern: Flutter with Impeller still wins on raw rendering consistency, holding 60 to 120 fps under complex animation load. React Native with Fabric and Hermes V1 wins on cold start (about 200 ms faster) and on battery (about 12% less drain under comparable workloads). For standard UI screens (lists, forms, navigation, networked data) both frameworks land at 58 to 60 fps and are indistinguishable from native to the end user.

That covers 80 to 90% of mobile apps. The honest framing is that cross-platform stopped being a feature compromise around 2024 for the CRUD-plus-occasional-animation app most teams are actually shipping. The exceptions are products where the value sits in the last 10% of native polish: 3D rendering, AR pipelines, low-level audio, complex camera workflows beyond what react-native-vision-camera handles, or sustained 120 fps gesture interaction.

Independent benchmarks vary on the specific numbers, especially the standard-UI fps figures. Treat them as direction-of-travel, not contract. For most enterprise mobile work in 2026, React Native is performance-equivalent to the user, and the choice comes down to ecosystem, team skills and total cost of ownership rather than frames per second.

What it actually costs in Australia in 2026

Live SEEK data in May 2026: roughly 222 React Native roles listed in Sydney, of which about 67 explicitly require React Native in the title. Brisbane is thinner. Glassdoor's averaged AU salary sits at AUD 127,425 (March 2026), with a second source at AUD 114,999. Sydney senior contract rates run up to AUD 200K base plus super; Sydney mid-level (4 to 6 years) lands near AUD 139K. Brisbane is roughly 10 to 15% lower depending on seniority. Contract rates run AUD 50 to 95 per hour.

React Native developers carry a 15 to 35% premium over plain React developers in Australia, reflecting the extra expertise needed across the native-bridge surface. The pool is real but tight. For a mid-market product team, hiring one senior RN lead in Sydney costs roughly the same as one mid-level iOS engineer plus one mid-level Android engineer combined (about AUD 240K).

The cost-out lever that most agencies do not surface is the hybrid model. One senior AU lead at around AUD 150K plus two mid-level Philippines team members at around AUD 60K combined lands a three-person team for about AUD 210K per year, which delivers more than the two-developer AU-only equivalent. drtalk has run on exactly this shape for six years (Brisbane HQ, Philippines pair, two to three hour time-zone overlap), shipping a Good Design Award-winning healthcare-grade app the whole way through.

The AI-tooling shift

The 2026 productivity story is the AI-coding tooling layer. GitHub Copilot reported 4.7 million paid subscribers as of January 2026, a 75% year-on-year jump, and scores 56% on SWE-Bench. Cursor scores 51.7%, runs roughly 30% faster autocomplete than Copilot, and raised USD 2.3 billion at a USD 29.3 billion valuation in November 2025. Both tools cost around USD 20 to 39 per developer per month.

Teams report cycle-time gains of around 40% with these tools, with Cursor specifically delivering about a 25% productivity uplift. No public benchmarks isolate React Native productivity from generic React or TypeScript, but Copilot's training data is heavy on the React stack and the day-to-day numbers transfer.

This shifts the calculus engineering leaders set in 2019. The old argument was "you need two native teams but each ships faster." The 2026 argument is "you need one cross-platform team, but each developer ships 40% more than the 2019 baseline." That collapses headcount and burn for any app where cross-platform is plausible at all, which is most enterprise mobile work.

Who is shipping it in production

Shopify runs all of their mobile apps on React Native today, handling millions of daily transactions with performance that matches their prior native builds (per Shopify Engineering's own writeups, source 3). The broader 2025 production-user enumeration below comes from Callstack's "React Native Wrapped 2025" year-in-review (source 5): Microsoft ships Office (Word, Excel, PowerPoint) on React Native, including the new Copilot AI features, and uses RN for Windows and Mac variants too. Discord runs hundreds of millions of users at sub-100 ms interaction latency on RN, processing billions of messages per day. Meta's Instagram, Facebook and Marketplace surfaces are partly on it. Tesla, Coinbase, Walmart, Bloomberg, Pinterest, Uber Eats, Wix, Salesforce, PUMA and Strava all have React Native in production. Aggregate global footprint is estimated at roughly 11 million live apps per the same Callstack analysis (figure is ecosystem-tracked, not audited; treat as directional).

The Airbnb counter-example from 2018 is the one consistently cited against React Native. The technical complaints in that post (async bridge, native dependency management) map directly onto the things Fabric, TurboModules and JSI were built to fix. No comparable household-name migration away from React Native has been published in 2024 to 2026.

The decision framework

Choose React Native when:

• The app is primarily forms, lists, navigation and networked data (80 to 90% of mobile apps)
• Your team already has React and TypeScript skills, giving immediate productivity
• You need both iOS and Android shipped under a tight budget
• You want a single codebase serving app and web (Expo Router enables this cleanly)
• Time-to-market matters more than the last 10% of native polish
• Your customers will not notice 50 ms of extra cold start

Do not choose React Native when:

• Your product is rendering-heavy: 3D, real-time video editing, AR overlays, complex animations beyond what Reanimated 4 and Skia handle
• You need deep native integration: custom Bluetooth stacks, sensor arrays, low-level audio routing
• Sub-100 ms cold start is a competitive differentiator
• Battery life is the headline product attribute (real-time tracking, background-heavy apps)
• Your team is primarily mobile-native engineers with no JavaScript background and switching would discard their expertise
• You have heavy platform-only design requirements (e.g. the latest iOS-only widgets where parity lags)

The honest one-line framing: React Native gets you to 90% of native at 50% of the cost. The question is not whether 90% is enough, because it usually is. The question is whether the specific 10% you are losing matters for your particular app. For most enterprise mobile work in 2026, it does not.

Donnish runs onshore (Australia) and offshore (Philippines) React.js and React Native developers under one roof. Most agencies pitch one or the other. The Donnish shape is an AU lead as single point of accountability, working with Philippines team members on a two to three hour time-zone overlap. drtalk is six years of production evidence that this works. If you are working through a 2026 mobile build decision and want a second opinion on the stack and the team shape, tell us about it.

Sources

1. React Native team, "React Native 0.84: Hermes V1 by Default", official release blog, February 2026. https://reactnative.dev/blog/2026/02/11/react-native-0.84
2. React Native team, "New Architecture", official architecture landing page. https://reactnative.dev/architecture/landing-page
3. Shopify Engineering, "React Native is the Future of Mobile at Shopify", engineering blog. https://shopify.engineering/react-native-future-mobile-shopify
4. Gabriel Peal (Airbnb Engineering), "Sunsetting React Native", June 2018, included as the historical counter-example. Technical complaints (async bridge, native dependency management) are the issues that the New Architecture was built to fix. https://medium.com/airbnb-engineering/sunsetting-react-native-1868ba28e30a
5. Callstack, "React Native Wrapped 2025: a month-by-month recap of the year", January 2026. https://www.callstack.com/blog/react-native-wrapped-2025-a-month-by-month-recap-of-the-year
6. Expo SDK 54 changelog (precursor to SDK 55) and SDK 56 Beta changelog, release cadence reference. https://expo.dev/changelog/sdk-54 and https://expo.dev/changelog/sdk-56-beta
7. SEEK, live React Native developer job listings, Sydney and Brisbane, queried May 2026. https://au.seek.com/react-native-developer-jobs/in-All-Sydney-NSW and https://www.seek.com.au/react-native-jobs/in-All-Brisbane-QLD
8. Glassdoor, "React Native Developer Salary in Australia", accessed March 2026. https://www.glassdoor.com.au/Salaries/react-native-developer-salary-SRCH_KO0,22.htm
9. TheirStack, "Companies using React Native in Australia", technology directory. https://theirstack.com/en/technology/react-native/au
10. Cursor + GitHub Copilot productivity numbers (2026) and subscriber counts: cross-sourced from practitioner comparisons. See e.g. https://ralphable.com/blog/cursor-vs-github-copilot-2026-ai-code-editor-showdown. Treat productivity-uplift figures as upper-bound directional indicators, not contractual.
11. drtalk production evidence, Donnish operations, 2020 to 2026. Six years of React Native in production for a Good Design Award-winning healthcare-grade app, Brisbane lead with Philippines pair. Per-engagement detail available on request.