<!-- mobian-agent-page publisher="dailydev" canonical="https://daily.dev/posts/react-navigation-8-0---march-progress-report-jff1bnvhh" -->

---
title: React Navigation 8.0 - March Progress Report | daily.dev
description: React Navigation shares a progress update on version 8.0 since its first alpha in December 2025. The release now requires React 19+, React Native 0.83+, and...
canonical: https://daily.dev/posts/react-navigation-8-0---march-progress-report-jff1bnvhh
twitter:card: summary_large_image
twitter:site: @dailydotdev
og:type: website
og:site_name: daily.dev
og:title: React Navigation 8.0 - March Progress Report | daily.dev
og:description: React Navigation shares a progress update on version 8.0 since its first alpha in December 2025. The release now requires React 19+, React Native 0.83+, and...
og:url: https://daily.dev/posts/react-navigation-8-0---march-progress-report-jff1bnvhh
og:image: https://api.daily.dev/og/posts/jFF1bnVhh.png
og:image:alt: React Navigation 8.0 - March Progress Report
og:image:width: 1200
og:image:height: 630
og:locale: en
---

> ## Documentation Index
> Fetch the complete documentation index at: https://daily.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# React Navigation 8.0 - March Progress Report

**[React Navigation](https://daily.dev/sources/react-navigation)** · 8 min read · 0 upvotes · 0 comments

## Summary

React Navigation shares a progress update on version 8.0 since its first alpha in December 2025. The release now requires React 19+, React Native 0.83+, and Expo SDK 55+ to support modern features like React.Activity, Suspense, and PlatformColor. Highlights include a new inactiveBehavior option for controlling how unfocused screens are handled, deep linking enabled by default in static configuration, Standard Schema support (Zod, Valibot, ArkType) for linking params, native SF Symbols and Material Symbols components, new Material Design 3 themes using PlatformColor, a UNSTABLE_CornerInset component for iPadOS windowed mode, a breaking change to getId behavior in stack navigators, web accessibility improvements using the inert attribute, expanded devtools logging, and LLM-friendly documentation formats. A beta is planned once a rewritten react-native-screens integration is ready.

## Full article

daily.dev links to this article rather than hosting it. Read it at the original source: <https://reactnavigation.org/blog/2026/03/10/react-navigation-8.0-march-progress>

## Questions this post answers

### What are the minimum requirements for React Navigation 8?

React Navigation 8 requires React 19 or later to support features like Activity and the use hook, which in turn means React Native 0.83 or later, or Expo SDK 55 or later. Upgrading below these versions will not work with the new alpha release, since it relies on these newer React and React Native APIs internally.

_Track library requirement bumps like this on daily.dev before planning a React Native upgrade._

### How does the getId behavior change in React Navigation 8 stack navigators?

In React Navigation 8, getId no longer rearranges the stack to bring an existing route to the front; instead it matches routes by ID similarly to route names. If already on a screen with the same ID, params update without pushing a new screen; if on a different screen, a new screen is pushed; with pop: true, it pops back to the matching route. This is a breaking change from React Navigation 7's behavior, made because the old rearranging logic caused broken behavior with Native Stack Navigator.

_Developers migrating to React Navigation 8 can follow breaking-change coverage like this on daily.dev._

### How do I enable deep linking in React Navigation 8 without extra configuration?

Deep linking is enabled by default in React Navigation 8 when using static configuration, with no need to pass linking-related options. Paths are auto-generated from screen names by converting PascalCase to kebab-case, and custom patterns or parsing can still be added per screen; it can also be explicitly disabled if not wanted.

_Keep up with navigation library changes like this deep-linking default on daily.dev while building React Native apps._

## Similar posts on daily.dev

- [React Navigation 8.0 - July Progress Report](https://daily.dev/posts/react-navigation-8-0---july-progress-report-zwpb6nosh) · React Navigation · 7 upvotes · 2 comments
- [React Navigation 8.0 Alpha with Native Bottom Tabs, Reworked TypeScript Inference and History](https://daily.dev/posts/react-navigation-8-0-alpha-with-native-bottom-tabs-reworked-typescript-inference-and-history-baby9kbnm) · InfoQ · 6 upvotes · 1 comments
- [React Native 0.83, Reanimated 4.2, State of RN, Refined, Crypto, Worklets, Sheet Navigator](https://daily.dev/posts/react-native-0-83-reanimated-4-2-state-of-rn-refined-crypto-worklets-sheet-navigator-xx7s6aqer) · This Week In React · 28 upvotes · 0 comments
- [React 19.2, New DevTools features, no breaking changes · React Native](https://daily.dev/posts/react-19-2-new-devtools-features-no-breaking-changes-react-native-0d1dqgcc6) · React Native · 69 upvotes · 1 comments
- [Making React Native actually native](https://daily.dev/posts/making-react-native-actually-native-bdan1xdzt) · Bytes by ui.dev · 2 upvotes · 0 comments

---

Tags: [#react](https://daily.dev/tags/react), [#typescript](https://daily.dev/tags/typescript), [#react-native](https://daily.dev/tags/react-native)

[View this post on daily.dev](https://daily.dev/posts/react-navigation-8-0---march-progress-report-jff1bnvhh)

```json
{"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]}
{"@context":"https://schema.org","@type":"TechArticle","headline":"React Navigation 8.0 - March Progress Report","url":"https://daily.dev/posts/react-navigation-8-0---march-progress-report-jff1bnvhh","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/react-navigation-8-0---march-progress-report-jff1bnvhh"},"datePublished":"2026-08-23T12:22:14.344Z","dateModified":"2026-08-23T12:44:31.739Z","description":"React Navigation shares a progress update on version 8.0 since its first alpha in December 2025. The release now requires React 19+, React Native 0.83+, and...","image":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/2cb5a266a09c2095f5194cd07eb12a75?_a=AQAEuop","thumbnailUrl":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/2cb5a266a09c2095f5194cd07eb12a75?_a=AQAEuop","isAccessibleForFree":true,"articleSection":"React Navigation","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"React Navigation","logo":"https://media.daily.dev/image/upload/s--d1x9LTh1--/c_limit,w_256/f_auto,q_auto/v1787487486/logos/react-navigation?_a=BAMAMicg0","url":"https://daily.dev/sources/react-navigation"},"commentCount":0,"discussionUrl":"https://daily.dev/posts/react-navigation-8-0---march-progress-report-jff1bnvhh","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":0},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":"react,typescript,react-native","timeRequired":"PT8M"}
{"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"React Navigation","item":"https://daily.dev/sources/react-navigation"},{"@type":"ListItem","position":3,"name":"React Navigation 8.0 - March Progress Report"}]}
{"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/react-navigation-8-0---march-progress-report-jff1bnvhh#faq","mainEntity":[{"@type":"Question","name":"What are the minimum requirements for React Navigation 8?","acceptedAnswer":{"@type":"Answer","text":"React Navigation 8 requires React 19 or later to support features like Activity and the use hook, which in turn means React Native 0.83 or later, or Expo SDK 55 or later. Upgrading below these versions will not work with the new alpha release, since it relies on these newer React and React Native APIs internally. Track library requirement bumps like this on daily.dev before planning a React Native upgrade."}},{"@type":"Question","name":"How does the getId behavior change in React Navigation 8 stack navigators?","acceptedAnswer":{"@type":"Answer","text":"In React Navigation 8, getId no longer rearranges the stack to bring an existing route to the front; instead it matches routes by ID similarly to route names. If already on a screen with the same ID, params update without pushing a new screen; if on a different screen, a new screen is pushed; with pop: true, it pops back to the matching route. This is a breaking change from React Navigation 7's behavior, made because the old rearranging logic caused broken behavior with Native Stack Navigator. Developers migrating to React Navigation 8 can follow breaking-change coverage like this on daily.dev."}},{"@type":"Question","name":"How do I enable deep linking in React Navigation 8 without extra configuration?","acceptedAnswer":{"@type":"Answer","text":"Deep linking is enabled by default in React Navigation 8 when using static configuration, with no need to pass linking-related options. Paths are auto-generated from screen names by converting PascalCase to kebab-case, and custom patterns or parsing can still be added per screen; it can also be explicitly disabled if not wanted. Keep up with navigation library changes like this deep-linking default on daily.dev while building React Native apps."}}]}
```

