navigation VS router

The collapsable header is built into the Android platform. That's why you see it on every Android app. Wrap your content in a CoordinatorLayout and the header automatically collapses. The Navigation router is the only navigation library for React Native that wraps the CoordinatorLayout. Take a look at the Twitter example to see the collapsing header in action

The reason so many apps have it is because it's built into the native Android api thanks to the CoordinatorLayout. The Navigation router is the only navigation library for React Native that wraps this native CoordinatorLayout. So you can do 100% native collapsing headers like this. Take a look at the twitter sample and you can see collapsing tabs on the Notifications screen, for example.

The Navigation router has already done this work for you. Take a look at the Twitter example. The notifications screen shows the sticky tabs and the timeline screen shows the collapsing header.

On Android, you can have whatever animations you want. Take a look at the medley sample where I animate all the scenes individually. The all come and go in different directions.

Make sure to give the Navigation router by u/grahammendick a try as well.

Oh that's weird. I think of the Navigation router as the router for React, too

Ryan Florence trains his fud gun on an unsuspecting developer. Will Navigation Man save the day? https://grahammendick.github.io/navigation/

Did you know that header scrolling animation is built into the Android platform? It's all taken care of by the CoordinatorLayout. My navigation library, the Navigation router, is the only one with a CoordinatorLayout component that renders to the in-built Android primitive. You can read more about it in the Navigation Bar docs or you can see it in action in the timeline page of the Twitter example. Hope this helps

Steps for building a simple mobile application using Expo SDK, Expo Router, and MongoDB Realm in React Native and plain Javascript.

In the video, I walk you through the code for an authentication flow using Expo Router and Appwrite.

Use expo-router to build native navigation using files in the app/ directory.

Nativewind v3 will be released soon Currently the author is working on https://github.com/expo/router/pull/498

If you manually edit the entry file to use a hardcoded string for the root path, does that work? Might also want to look here to debug https://github.com/expo/router/blob/main/packages/expo-router/babel.js

Expo is also working on expo-router which is file system based - it means that it could technically infer the nesting without having to manually do it.

How would you say the Navigation Router stacks up to the new expo-router?