You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As introduced on Slack, the tab approach has a downside that it feels a bit cumbersome looking at the current state:
When navigating to List tables you won't continue in a breadcrumb like fashion if you click an object relationship of an object in the List, and instead this will just go back to the object in the overall table of objects. The result is that a bread crumb isn't the right analogy with List tables. Instead it is more of a parent child relationship. A List is owned by the parent object.
When using tabs (or breadcrumbs) there isn't any space in the UI to include information about the list. You can quickly lose context on who owns the list.
To solve both of these issues, we came up with a different UI/UX:
The idea is that we abandon the tabs and simply make the left hand list of Classes be an accordion, where when you click a List from an object in a class, a row is expanded below the Class for the list.
In my mockup image, as a user I would be browsing the Person class when I decide to click on a List of dogs owned by the Person "John Smith". At this point the left-hand menu expands to include a new row that is indented to show that this is a List of Dog objects. The parent information could include a link back to "John Smith" and show that this came from the parent property dogs.
Browser must display related objects:
The text was updated successfully, but these errors were encountered: