Hi Jason, I wasn’t saying I saw any deficiency in Ember routing - I was finding it hard to see how I should best manage state in the given example. My thoughts centered around persisting each route as the user navigated deeper through the stack by nesting routes. That way, none of the parent routes in the stack would be torn down.
As it is, that’s clearly not the approach to take and the gap in my knowledge is ember-state-services. Thanks for the link!
In particular, this video from Oct '15 was really helpful. It explains how ember-state-services creates ‘buckets’ for different model instances. So as per the Facebook example, when navigating back through the stack, state such as scroll position can easily be recalled for multiple visits to different user profile pages (which reference the same route ‘user/:user_id’).
The only gotcha I can foresee is if the user was to visit the exact same route multiple times in one stack, but that can be managed.