I think I did a horrible job explaining why I personally dislike using the user page for this function.
If I am looking through my bookmarks or likes my “next action” is going to be one of the following:
- Go to a topic at my last read position
- Go to a topic at the bookmarked/liked position
- Go to my unread/new topics or home page
- Reorder list so I can see it by latest or something
By keeping the UI trappend in the user page we have this:
We just have a ton less UI to work which makes me feel:
“Oh no, I am headed to the user page where there lots and lots of options I don’t care about. 50% of my visual field is full of superfluous info”
Which is why I don’t particularly care about being there when I am doing work. I think the struggle the user page has is that there are two design constraints at strong odds.
- Show me information about another user
- Show me information about my stuff
Both, conceptually are at very strong odds, when I am looking at another user I am not trying to get work done, just snooping around and the extra information is super useful. So we designed well for this use case.
When I am looking at my stuff all the decoration is superfluous which is not ideal.
I completely agree with the critic of “What am I looking at when filters are enabled? Where am I?” its a general issue we have with all our topic list filters, we should have a solution for this. However resolving it is at most just adding 1 more element on the page (when data is filtered), not 30 elements and taking up 50% of the visual field.
This widget could be made smarter to deal with filters etc:
On mobile this issue is even more egregious cause real estate is so limited.