User Experience Stack Exchange is a question and answer site for user experience researchers and experts. It only takes a minute to sign up.
Sign up to join this community
Let's say I have an app that manages some items. An item can be "owned" by an user. I'll have these screens :
I want to display information about the user that owns the item on (B) and link that to that user's detail page (C).
Also, on (C) I'd like to have the list of items owned by him and link them to the item detail pages accordingly(B)
This is what the navigation can get to, which doesn't seem right:
(A)->(B)->(C)->(B)->(C)...
Given the scenario the navigation you outline is what you get.
Yes, it can be confusing, but it is the logical outcome of your workflow. I can't see a way to change this without breaking the navigation.
Most people won't really notice this. They'll probably hit "home" to get back to the list of items (assuming that it exists) rather than using any "back" button you might have.
I'm not sure that I see anything wrong with your flow.
I see A as your home screen (which should have a nav item or breadcrumb trail of some sort to get back to it from other screens) and once they go into an item detail and want to know more about a user's other items, it would be confusing to not see the item they just came from in the user's items list.
So, A > B > C > B > C > B > C > A would be fine depending on the goals of the site and the goals of the user.
Just make sure they have easy ways to get back to A and you should be golden.
