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

Welcome to the first article of a series where we will explore TanStack Router, a new router for React (version 1.0 released in December 2023).

Tanstack - Tanstack has evolved to an entire ecosystem consisting of the famous Tanstack (or React) Query, Tanstack Table, now also Tanstack Router and Tanstack Form. It started with Tanstack Query, which adopted Nx and Nx Cloud. Zack talked about this collab with Dominik, and we also had Dominik on our Nx live stream. Now, all the above-mentioned Tanstack libs have adopted Nx, and there's more coming.

We've found that `tanstack/router` was patched to make HMR work as expected, but this solution doesn't work for us, as our config is not a class: https://github.com/TanStack/router/commit/9f2150190a628fb3767ca8ad0d8634b357f43c51

Start a discussion about what you'd like to see and I'll do my best. https://github.com/tanstack/router/discussions

React Location certainly needs more attention in the React community. React Location also has a grooving community you can find on StackOverflow, Discord, and GitHub discussions. Finally, I invite you all to try out React Location and see how fantastic a routing solution is.

Enterprise Client-Side Routing for React Enjoy this library? Try the entire TanStack! React Query, React Table, React Charts, React Virtual Visit react-location.tanstack.com for docs, guides, API and more!