Filters

A filter bar is the row of controls above a table, catalogue or result list that narrows what is shown without changing what is stored: a date range, a segmented switch between states, a set of removable chips each holding one condition. Conditions combine, so the bar has to say plainly which ones are on, and let any single one be taken off without rebuilding the rest.

Filter state is application state and repays being treated as such: put it in the URL, so a narrowed view can be reloaded, sent to a colleague and linked from a report. The failure mode here is quiet. A filter left on from an earlier session makes a full table look empty, and what gets reported is missing data rather than a control nobody could see. Showing the result count beside the controls, giving every chip its own clear button and the bar a single reset, is what keeps that from happening.

12 blocks

Calendar

Dashboards, reports, anything scoped to a date range

Calendar, the period drawn as days; the range is a band you drag

Activity over time, where people think in shapes of days rather than in dates

Calendar, say the range; the card shows what it understood

People who know the range they want and would rather say it than click through a calendar

Table

Data tables, transaction lists, record browsers

Table, the switch carries the money; sorting moves into the headers

Ledgers where the totals matter as much as the rows

Table, filters and sort become a saved tab

Tables people return to with the same filters: save a setup as a tab

Chips

Advanced filtering, faceted search, saved-filter bars: several fields, operators and values at once

Chips, see what a value does before you pick it

Large lists where people want to know what a filter does before they commit to it

Chips, the filters read as one sentence

Reports and saved views where the filters should read like a question

Selectable chips

Filters picked by tapping, one answer or several

Selectable chips, counts

Faceted filters where people should see what a choice would show before they make it

Selectable chips, selection bar

Filter sets where the actions should only appear once something is picked

01

Using Filters

Reach for it when

  • A table long enough that scanning it is slower than narrowing it
  • Records scoped by time, where a preset range answers most of the questions asked of them
  • A catalogue with facets people combine: status and type and owner at once
  • A result list where conditions need to come off one at a time

Reach for something else when

  • Only a handful of rows exist: sorting, or nothing, beats a bar of controls over a short list
  • Each person wants a different fixed view of the same set: saved views or tabs carry that better than filters reapplied by hand every visit
  • The query is free text across everything rather than a narrowing by field. That is a search field, or a command menu when it spans kinds
02

Where it shows up

01

Transaction browsers

A ledger opens on everything and is read by narrowing: income or expenses first, then a sort, then a search inside what is left. The segmented switch carries the exclusive choice and the rest stacks on top.

02

Date-scoped reporting

A dashboard answers questions about a period, so the range is the primary control: a preset list for the common answers, a shortcut back to today, and the resolved range shown as text beside it.

03

Faceted catalogues

Chips hold one condition each, so somebody adds status, then type, then owner, and drops whichever turned out not to matter. An unset chip still names its field, which is how people learn what can be narrowed.

04

Admin record browsers

Support and operations staff work the same large tables all day. The value is removing one condition at a time rather than composing a fresh query for every question a customer asks them.

03

Questions

Should filters apply immediately or behind an Apply button?

Apply immediately when results are cheap to fetch and the change is visible, because that feedback is how people learn the way the filters combine. Use an explicit Apply when each query is expensive, when several fields are normally set together before anything is run, or on a long panel of criteria where partial states would fire a run of useless requests.

How do you show that filters are currently active?

All blocks
The Orvain Dispatch

Premium components, free in your inbox.

Join the Orvain Dispatch and get production-ready components, free to keep: React and Vue code plus the Figma frame, yours to ship.

Just components, never spam. You can unsubscribe anytime.