nostr:npub1jjqptjtv5jgsgdsplfs8ndnwt44zn0gv2jcsut77t37pgcahxuss6aksgt 
Google did come to this from the dead-trees, static, web/document model, wherein a linear progress works semi-OK like a browser. 

In the mobile/app universe the notion of wanting to go “back” is contextually slippery: previous page, one step back inside the current app, back to previously used app, all the way to Home? What happens when an action on current page changes state and you go “back”, what does the app show now (old|new state)? What does a random *user* expect to see?