A peek into React Navigation 7

Sahoo contrasts the dynamic API introduced in React Navigation 5 with the static APIs in versions 1 through 4. Dynamic navigation supports conditional and lazy rendering, but makes it difficult to derive types and deep links without duplicating the navigation structure. The new static API is an optional addition built on the existing dynamic API, so apps do not need to be rewritten.

The static API defines screens in an object keyed by screen name, with components, options, and linking configuration. `createStaticNavigation` turns that navigator into a component similar to `NavigationContainer`. The `StaticParamList` helper infers types from the root navigator and nested navigators, reducing the manual type definitions needed for autocomplete.

The static API adds an `if` option that takes a React hook returning a Boolean, allowing screens to appear or disappear based on authentication state. Sahoo also says static and dynamic navigators can be used together, such as embedding a static-configured component inside a dynamic navigator when screens depend on backend data.

React Navigation 7 includes a standalone drawer package for cases where a drawer is needed without a navigator. It also adds custom tab transition animations and a side layout for bottom tabs, with options for a custom sidebar. This avoids swapping between separate drawer and tab navigators on resize, which could discard navigation history and local form state.

Other planned or included changes mentioned are better right-to-left support, a `popTo` method that returns to a named screen with parameters, and component updates based on newer Material Design. Sahoo directs attendees to the alpha at reactnavigation.org/next and asks them to test it and report bugs or improvements; he notes that the documentation is incomplete.