React Native 0.87 strips out deprecated APIs in its biggest cleanup yet — a sign the framework is finally closing in on a 1.0

React Native 0.87 removes long-deprecated APIs like InteractionManager and SafeAreaView and restricts deep path imports, a cleanup release developers are reading as the clearest signal yet that a stable 1.0 is within reach after years of it being 'on the horizon'.

React Native 0.87 doesn’t add much. It removes things — old APIs like InteractionManager and SafeAreaView that have been deprecated for years, plus tighter restrictions on deep path imports that let developers reach into the framework’s internals in ways the core team never fully supported. Developers tracking the release are calling it the biggest cleanup in the framework’s recent history, and reading it as exactly what a shrinking API surface ahead of a 1.0 release looks like.

That matters because React Native 1.0 has been “on the horizon” for the best part of a year with no confirmed date, which has made version stability a genuine hesitation for teams choosing between it and Flutter, SwiftUI, or Kotlin Multiplatform. A framework that’s still actively removing and restructuring core APIs is a framework whose upgrade path can break your app between minor versions — a real cost when you’re maintaining a production cross-platform codebase rather than a demo. Cleanup releases like 0.87 are the unglamorous prerequisite to that stability, not a feature in themselves, but they’re the leading indicator worth watching if API churn has been the reason you’ve held off committing.

None of this changes what React Native is good at today — one JavaScript/TypeScript codebase shipping to iOS and Android with near-native performance for most business apps, backed by the largest community of any cross-platform framework. It does mean the “wait for it to stabilise” objection is getting harder to justify as the gap narrows.

So what

If cross-platform framework maturity has been a reason to delay a mobile build, React Native’s trajectory toward 1.0 is a signal worth revisiting rather than a reason to keep waiting — the alternative is usually a slower, costlier native-per-platform build for capability most business apps don’t need. We build across React Native, Flutter, and native iOS/Android depending on what the app actually requires; see our cross-platform and iOS & Android services or start a project if you’re weighing frameworks for a build.

← All research

More research.

VS Code 1.145 lets Copilot run local automations on a schedule with custom agents

GitHub's 6 November 2026 Copilot weekly release adds cron-scheduled local automations with custom agents in VS Code 1.145, alongside Copilot in JetBrains Air and a unified Copilot CLI settings dashboard.

Read ›

@GitHub in Slack and Teams is generally available: from a chat message to a pull request

GitHub's 6 November 2026 release makes @GitHub in Slack and Teams generally available, letting teams investigate bugs, create issues and open pull requests with an AI coding agent from a chat conversation.

Read ›

GitHub secret scanning cuts false alarms for AWS, Google and Alibaba cloud keys and adds a SpaceX detector

GitHub's 5 November 2026 secret scanning update tightens detectors for AWS, Google Cloud and Alibaba keys, relevant to teams building software with AI coding tools that can paste credentials into code.

Read ›

GitHub's Copilot code review can now be managed by API, with review effort levels and AI credit costs shown

GitHub's 6 November 2026 update lets organisations manage Copilot code review by API and see the review effort and AI credits each AI code review used, a sign AI-assisted development is becoming auditable.

Read ›

GitHub's Copilot impact dashboard now counts chat and VS Code agent use, and drops the 'passive users' label

On 6 November 2026 GitHub added Copilot Chat and the VS Code Agents window to its Copilot impact dashboard, bringing it to nine tracked experiences, and renamed 'Passive users' to 'Chat-first users'.

Read ›

Claude Code 2.1.319: a setting that denies permission prompts so AI agent runs don't stall

Claude Code 2.1.319 (6 November 2026) adds a permissions.denyInsteadOfPrompting setting and moves long MCP tool calls to the background, a sign AI-assisted development is being built for unattended runs.

Read ›

Start a project

Building with AI? Let's talk.

Tell us what you are building. We'll give you an honest view of the right approach.

Start a projectSee our work