The purpose of the go_router for Flutter is to use declarative routes to reduce complexity, regardless of the platform you're targeting (mobile, web, desktop), handling deep linking from Android, iOS and the web while still allowing an easy-to-use developer experience.
Could you please share an example of how to best deal with the situation where we might have different navigation structures depending on the screen real estate? For example, on smartphones, I would like /users/john to stack 2 screens, one for the list of users and another one for the user details for john. But on a tablet or on the web, I would like to stack just one split screen, with the left part listing users, and the right part showing the user details (nested navigation). It seems to me like it's a very common use case, but I don't see how to do it after reading the doc.
Could you please share an example of how to best deal with the situation where we might have different navigation structures depending on the screen real estate? For example, on smartphones, I would like /users/john to stack 2 screens, one for the list of users and another one for the user details for john. But on a tablet or on the web, I would like to stack just one split screen, with the left part listing users, and the right part showing the user details (nested navigation). It seems to me like it's a very common use case, but I don't see how to do it after reading the doc.