---
title: "React Navigation | Skills We Assign For | Azendo"
description: "React Navigation in React Native apps — navigator structure, deep linking and typing, plus the Azendo roles assigned for it."
url: "https://azendo.co/skills/react-navigation/"
---

[Skills](https://azendo.co/skills/) Mobile platforms and frameworks 

# React Navigation.

React Navigation is the standard routing library for React Native: stack, tab and drawer navigators composed into a tree, with deep linking, typed route parameters and state persistence handled by the library rather than by the application.

## Where React Navigation fits on a long engagement.

Navigation structure is one of the earliest decisions and one of the most expensive to revisit, because it determines what deep links are expressible and where state can live. A navigator tree assembled ad hoc as screens were added is the usual reason a deep-link requirement later turns out to be awkward rather than trivial.

Typed routes are worth the setup. Without them, parameters are an untyped object and a renamed field is a runtime failure on a screen nobody tested; with them it is a compile error. On a codebase with dozens of screens that difference compounds quickly.

## What an assigned team does with React Navigation.

Deep linking is usually specified late, by marketing or by a partner integration, against a navigation structure that was not designed for it. Handling that well means treating the link surface as an interface rather than an afterthought.

That is the same discipline as any other external contract, and it is held by the assigned specialists over the life of the product rather than solved once. How that responsibility is framed is described in [how an assignment runs](https://azendo.co/how-it-works/).

## What we use React Navigation for.

* A navigator tree that supports deep links Structure chosen so campaign and notification links reach the right screen with the right state.
* Typed route parameters Screen arguments checked at build time, so a rename fails the build rather than a user session.
* State restored after a cold start Navigation persistence so returning users land where they left rather than at the root.

## How React Navigation capacity is assigned.

Navigation work sits inside React Native capacity under [outsource software development services](https://azendo.co/services/software-development/).

## Roles we assign React Navigation for

* [React Native Developer Mobile development](https://azendo.co/services/mobile-development/react-native-developer/)

## Service lines it sits in

* [Mobile development](https://azendo.co/services/mobile-development/)

Capacity is agreed as a committed monthly capacity across a discipline, not per skill.

## Related in mobile platforms and frameworks

* [SwiftUI — skill we assign for](https://azendo.co/skills/swiftui/)
* [UIKit — skill we assign for](https://azendo.co/skills/uikit/)
* [Jetpack Compose — skill we assign for](https://azendo.co/skills/jetpack-compose/)
* [Coroutines — skill we assign for](https://azendo.co/skills/coroutines/)
* [Flutter — skill we assign for](https://azendo.co/skills/flutter/)
* [React Native — skill we assign for](https://azendo.co/skills/react-native/)
* [Expo — skill we assign for](https://azendo.co/skills/expo/)
* [Ionic — skill we assign for](https://azendo.co/skills/ionic/)

## Tell us what your roadmap needs React Navigation for.

A service delivery manager replies with the disciplines we would assign, the monthly capacity and what the first month looks like.

[All skills we assign for](https://azendo.co/skills/)