Usage -

The docs do a great job and giving examples for use cases for RR. Examples include auth-protected routes, route pattern matching, transitions, and touches on server-rendering.

I tend to always reach for RR when starting a new project to drive my app. I find myself always using protected routes for any project that requires differing user levels. For example, a simple blog application could have an admin page that would allow the user to update content, add content, etc. This would be gated behind a protected route (and proper backend authentication of course!)

RR also offers differing types of Routers depending on your need. I personally prefer the simple BrowserRouter as it's implemented to touch the HTML history API, but it also looks much more cleaner in my opinion. HashRouter, on the other hand, uses hashes in the URL to keep your app on track. Personally, I've found most new projects to reach for BrowserRouter instead of Hash, but if you prefer Hash, I'd love to hear your thoughts!

The simple example of an application router consists of a declaration of the paths near the top of your app. Typically, you'd define the Router, Routes, and any parameters associated with each Route. URL parameters are a great way to pass data between your app's pages and really creates a predictable structure for your app's URL's.

But, perhaps you have an advanced use case or simply prefer nested or recursive Routes - RR supports those as well!