React Native Roadmap 2026-W38

Week of September 14–20, 2026

Items This Week

#	Title	Label	Link
1	Shopify is moving away from React Native to native	🟦 RN	Read
2	React Native 0.88 RC.1 — React 19.3 support	🟦 RN	Read
3	You don't need a Mac to develop iOS apps anymore	🟧 EXPO	Read
4	Expo SDK 58 Beta	🟧 EXPO	Read
5	Screenmap — visual navigation maps for Expo and React Native apps	🟧 EXPO	Read

5-Day Action Plan

🟦 RN Chunk 1 — Run a New Architecture readiness audit

Goal: Identify the concrete migration work needed to improve startup, stability, and performance without deciding to rewrite the app natively.

Source: Shopify native migration case study

Scope:

Audit inventory legacy-architecture dependencies and native modules.
Audit measure one startup and one stability baseline.
Audit list blockers that prevent New Architecture adoption.
Audit create a prioritized remediation backlog with one small quick win.

Out of scope: A native rewrite, a full migration, and attributing all performance issues to React Native without measurement.

Dependencies: Access to the app's native dependency graph and one representative release build.

**Acceptance criteria:

The audit names each blocker and its owning package or app module.
Startup and stability baselines are reproducible.
The team has one prioritized remediation suitable for a one-day follow-up.
No production architecture switch is made by this chunk.

Estimated effort: M

**Copy/paste this prompt:**

Implement the following React Native chunk for your mobile app:

Goal: Identify the concrete migration work needed to improve startup, stability, and performance without deciding to rewrite the app natively.

Files to create or modify:

docs/new-architecture-audit.md
scripts/native-dependency-report.mjs
docs/performance-baseline.md

Implementation instructions:

Collect dependency and architecture flags from the current app.
Run one cold-start and stability measurement.
Classify blockers as app-owned, dependency-owned, or unsupported.
Publish the audit and select the smallest high-value remediation.

Acceptance criteria verification checklist:

The audit names each blocker and its owning package or app module.
Startup and stability baselines are reproducible.
The team has one prioritized remediation suitable for a one-day follow-up.
No production architecture switch is made by this chunk.

🟦 RN Chunk 2 — Validate React Native 0.88 RC.1 with React 19.3

Goal: Confirm that the release candidate can be evaluated safely with the React 19.3 feature set before planning an upgrade.

Source: React Native 0.88 RC.1

Scope:

Test create a validation build using RN 0.88 RC.1.
Test smoke-test navigation, gestures, lists, and error reporting.
Test check whether React 19.3 APIs affect shared or platform-specific code.
Test record regressions and a rollback decision.

Out of scope: Adopting experimental React 19.3 APIs in production and upgrading unrelated packages.

Dependencies: A reproducible branch and device/simulator coverage for the app's critical flows.

**Acceptance criteria:

The validation build launches on iOS and Android or lists exact blockers.
Critical flows pass without new crashes or visual regressions.
React 19.3-related behavior is explicitly recorded.
The main branch remains unaffected until approval.

Estimated effort: M

**Copy/paste this prompt:**

Implement the following React Native chunk for your mobile app:

Goal: Confirm that the release candidate can be evaluated safely with the React 19.3 feature set before planning an upgrade.

Files to create or modify:

docs/rn-0.88-rc1.md
package.json
ios/
android/

Implementation instructions:

Create the validation branch and capture current versions.
Apply the RC.1 upgrade using the supported toolchain.
Run critical-flow smoke tests and compare logs.
Document blockers, rollback, and upgrade recommendation.

Acceptance criteria verification checklist:

The validation build launches on iOS and Android or lists exact blockers.
Critical flows pass without new crashes or visual regressions.
React 19.3-related behavior is explicitly recorded.
The main branch remains unaffected until approval.

🟧 EXPO Chunk 3 — Run one iOS cloud-simulator smoke flow

Goal: Give Windows-based or CI contributors a repeatable way to verify one iOS flow without requiring a local Mac.

Source: Expo cloud simulators

Scope:

Configure configure access to the approved Expo cloud simulator service.
Configure create one deterministic launch-and-interaction flow.
Configure capture test artifacts and failure status.
Configure document cost, access, and limitations.

Out of scope: Replacing local iOS development, broad end-to-end coverage, and unattended production releases.

Dependencies: Expo cloud simulator access, a test account, and one stable smoke flow.

**Acceptance criteria:

A contributor can launch the selected iOS flow from the documented command.
The flow reports pass/fail with an accessible artifact.
Authentication material is stored outside the repository.
The documentation states when a local device or Mac is still required.

Estimated effort: S

**Copy/paste this prompt:**

Implement the following React Native chunk for your mobile app:

Goal: Give Windows-based or CI contributors a repeatable way to verify one iOS flow without requiring a local Mac.

Files to create or modify:

e2e/ios-cloud-smoke.yaml
scripts/run-ios-cloud-smoke.mjs
docs/ios-cloud-simulators.md

Implementation instructions:

Confirm service access and required project identifiers.
Write one stable smoke flow with explicit assertions.
Run it from a clean environment and save the artifact.
Document repeatability, limitations, and cleanup.

Acceptance criteria verification checklist:

A contributor can launch the selected iOS flow from the documented command.
The flow reports pass/fail with an accessible artifact.
Authentication material is stored outside the repository.
The documentation states when a local device or Mac is still required.

🟧 EXPO Chunk 4 — Create an Expo SDK 58 beta compatibility report

Goal: Assess the upcoming SDK's platform and tooling benefits without making the beta a production dependency.

Source: Expo SDK 58 Beta

Scope:

Evaluate create a beta-only validation branch or example app.
Evaluate check iOS 27, RN 0.88 RC, Expo Modules, Router, and widget claims relevant to the app.
Evaluate run the app's critical flow and build checks.
Evaluate document blockers and a stable-release adoption checklist.

Out of scope: Shipping the beta, migrating every package, and implementing every announced feature.

Dependencies: A separate validation branch and access to iOS/Android build environments.

**Acceptance criteria:

The beta branch builds or lists exact incompatibilities.
Relevant Expo Router and native-module behavior is tested.
The app's current dependency blockers are documented.
A stable-release checklist is ready for later use.

Estimated effort: M

**Copy/paste this prompt:**

Implement the following React Native chunk for your mobile app:

Goal: Assess the upcoming SDK's platform and tooling benefits without making the beta a production dependency.

Files to create or modify:

docs/expo-sdk-58-beta.md
package.json
app.json
eas.json

Implementation instructions:

Clone the current dependency and build configuration.
Apply the beta in an isolated branch.
Run critical flows and platform build checks.
Record findings and define stable-release gates.

Acceptance criteria verification checklist:

The beta branch builds or lists exact incompatibilities.
Relevant Expo Router and native-module behavior is tested.
The app's current dependency blockers are documented.
A stable-release checklist is ready for later use.

🟧 EXPO Chunk 5 — Add a Screenmap snapshot to mobile CI

Goal: Make navigation regressions visible in pull requests by generating a visual map of the app's screens.

Source: Screenmap

Scope:

Configure install Screenmap in a non-blocking CI job.
Configure capture the selected app routes with stable fixtures.
Configure publish the generated map or artifact on pull requests.
Configure document how reviewers interpret changes.

Out of scope: Visual testing of every edge case, replacing functional tests, and blocking all pull requests on first adoption.

Dependencies: A deterministic navigation entry point, CI device/emulator access, and artifact storage.

**Acceptance criteria:

The CI job captures the agreed screen set on a sample pull request.
The artifact is linked from the pull request checks.
A reviewer can identify an unintended navigation or layout change.
Initial failures are non-blocking and actionable.

Estimated effort: M

**Copy/paste this prompt:**

Implement the following React Native chunk for your mobile app:

Goal: Make navigation regressions visible in pull requests by generating a visual map of the app's screens.

Files to create or modify:

.github/workflows/mobile-screenmap.yml
e2e/screenmap-flow.yaml
docs/screenmap.md

Implementation instructions:

Choose stable routes and fixture data.
Configure Screenmap and the CI runtime.
Upload the map as a pull-request artifact.
Test one intentional visual change and document review steps.

Acceptance criteria verification checklist:

The CI job captures the agreed screen set on a sample pull request.
The artifact is linked from the pull request checks.
A reviewer can identify an unintended navigation or layout change.
Initial failures are non-blocking and actionable.