I'm researching Material Design in how it's related to layer based navigation.
Navigational directions Based on your app’s information architecture, a user can move in one of three navigational directions:
Lateral navigation refers to moving between screens at the same level of hierarchy. An app’s primary navigation component should provide access to all destinations at the top level of its hierarchy.
Forward navigation refers to moving between screens at consecutive levels of hierarchy, steps in a flow, or across an app. Forward navigation embeds navigation behavior into containers (such as cards, lists, or images), buttons, links, or by using search.
Reverse navigation refers to moving backwards through screens either chronologically (within one app or across different apps) or hierarchically (within an app). Platform conventions determine the exact behavior of reverse navigation within an app.
Does anyone know of any online examples of a mobile and desktop app that demonstrates this?
We see it in mobile app design everywhere, that's prolific. But how those layers translate between mobile to desktop layout is what I cannot find examples of.
You can see that these navigations are layers, where the back arrow is "upward" navigation to the page behind this book details layer. With the advent of PWAs we're going to see a LOT more of this in non-native design.
So how does this example translate to desktop size screens?
I'm starting to believe that layered navigation, as it is explained in Google's spec, is meant for native mobile and installable web apps where the browser's back/forward buttons no longer exist and we developers are responsible for integrating them.