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
Initial testing with ~100 stations showed that a mechanism to filter stations based on various criteria is a must-have. Sorting and grouping (#33) alone is just not enough.
This issue is to discuss and document what kind of filtering we are going to implement and how the UI for this should look like.
The text was updated successfully, but these errors were encountered:
This kind of UI features are actually usability optimizations, and just as with any optimizations they're relative to a particular use case...
... so my question is: What criteria is the one that we (or users) use to identify stations that is not being served by the dashboard right now. I mean, what are you looking for when you're looking for something? The station in a certain floor? The station running a certain app? The station with a certain name? The only one on?
Right now there's a filter for state, and the sorting to help finding things by name, app or profile. Any addition to the UI should be to make certain use cases simpler, but we need to be specific since it would take too much time to add every imaginable kind of filter (something that a lot of popular commercial apps don't even try to do).
Also I think that probably the naming of stations could perhaps be made more useful, since it's completely arbitrary... stations could be prefixed with the floor/location so ordering by name helps finding them more than the serial number.
Initial testing with ~100 stations showed that a mechanism to filter stations based on various criteria is a must-have. Sorting and grouping (#33) alone is just not enough.
This issue is to discuss and document what kind of filtering we are going to implement and how the UI for this should look like.
The text was updated successfully, but these errors were encountered: