make filters more fluid
a 'focus request' to improve filters UI & UX. filters are great! they can & should be improved in use, though!
– there is a cluster of requests around this.
and I think priority could / should be:
• less clicks;
• savable (maybe even: persistent) filters in the filter view (depending on object type?!);
• more instant feedback when filters are picked…
• 'group by' + some more refinements in criteria included (also in terms of UI integration)
I know, it kind of also drifts into the query question… and I think that separation should be revisited, which also harks back to older discussions on this (need for simplification in UI / UX level)
… it´s all not 'critical per se'. but it adds up to an experience of being chewy and pedestrian this way – while it really is one of the strong aspects of Capacities… 🌻
btw: I think there are still a lot of requests in the system re. better overall integration of 'fixed sets' (where tags = properties; and vice versa); and actually I think this has already been silently served in recent updates… so maybe the ticketbase here can be cleaned a little?! 😀
see:
👉 https://capacities.io/feedback/p/ability-to-store-different-views-with-different-filters-sorting-etc
👉 https://capacities.io/feedback/p/query-filtering-for-blocks-properties
👉 https://capacities.io/feedback/p/embedded-content-filters-tags
👉 https://capacities.io/feedback/p/allow-filtering-object-types-in-a-query-by-shared-property
👉 https://capacities.io/feedback/p/more-filter-options-current-week-month-year-dynamic-fixed-filters
👉 https://capacities.io/feedback/p/select-link-to-object-type-with-filters
👉 https://capacities.io/feedback/p/filtering-while-using-filter-for-collections-takes-very-long
0 Comments
Sign in to comment
No comments yet. Be the first to share your thoughts!
