When to use
- A list, table, or dataset where the user needs to locate specific items quickly.
- Content-heavy pages where scrolling to find something isn’t practical.
- Global search across the whole application (scoped to the Command).
When not to use
- Choosing from a known set of options — use Combobox or Select.
- Filtering by multiple attributes simultaneously — use filter controls alongside or instead.
- Free text input unrelated to finding content — use a plain Input.
Dos and don’ts
- Do scope the search clearly — make it obvious whether it’s searching the current list, the current page, or the whole app.
- Do show a no-results state when the query returns nothing; don’t leave an empty list with no explanation.
- Do debounce live search to avoid excessive requests while the user is still typing.
- Do use expected placeholder text that describes the scope: “Search assets” is more useful than “Search…”.
- Do make sure search and filters work together — applying a filter shouldn’t silently clear the search query.
- Don’t trigger search only on form submit if live filtering is possible — users expect immediate feedback.