Back to all posts
App UX7 min read·October 25, 2026

How Should Search and Filters Work in Your App?

TB
ThynkBlox Apps Team
App Engineering

Design mobile app search and filters as one journey: enter a query, narrow the results, inspect an item and return to the same list position. Keep the query, active filters and sort order visible, with a clear way to change each. Decide which choices persist and give people a useful next step when nothing matches.

What should people be able to search for?

Start with the task someone wants to complete. In a rental app, they might search for a neighbourhood or property name. In a stock catalogue, they might use a product name or item code.

Define the searchable fields before drawing the screen. If a search box accepts product names but ignores item codes, its label or supporting text should make that boundary clear.

Use a specific prompt such as “Search products or item codes” instead of “Search anything”. Keep the entered query visible after submission so people can correct it.

Choose whether results update while someone types or after they submit. For longer queries or costly searches, an explicit Search action may suit the task. For a short local list, updating as people type may be enough. Whichever approach you choose, avoid moving the list beneath someone while they are trying to select a result.

Which defaults should the first list use?

Choose a starting view that makes sense before anyone searches. That might be all available products, upcoming appointments or items in a location the person has already selected.

Treat any default that excludes items as a visible condition. If the list starts with “Available only”, show that choice and let people remove it unless availability is a fixed boundary of the screen.

Separate the screen’s scope from optional filters. A list inside a particular project can stay within that project, but the heading should identify it. An optional “Assigned to me” filter should remain visible and removable.

Before adding advanced controls, define the smallest useful search journey. Our guide on how to scope an app MVP can help you decide which choices belong in the first release.

How should filters work on a small screen?

Put frequent choices close to the list. Keep less common options in a clearly labelled Filters panel. Choose controls that match the decision: a single selection for one category, multiple selections for several acceptable brands, or labelled minimum and maximum fields for a range.

Write down how selections combine. A sensible catalogue rule might accept any selected brand while requiring the chosen availability and price conditions. Make that behaviour clear through labels and examples.

For a panel with several choices, an Apply button gives people a chance to finish editing. Keep draft changes separate from applied filters:

  • Apply updates the list.
  • Cancel or dismiss leaves the current results unchanged.
  • Reset restores the panel’s stated defaults.
  • Clear filters removes optional restrictions from the list.

For a single quick toggle, applying immediately can be simpler. Avoid mixing these behaviours within the same panel without explaining what will happen.

How can people keep track of active filters?

After the panel closes, show a compact summary above the results. Use readable labels such as “Available only” and “Colour: blue”, with a clear remove action for each.

A number beside Filters can signal that choices are active, but it should not be the only summary. People should be able to identify what is narrowing the list without reopening the panel.

Keep three actions distinct: clearing the query, clearing filters and resetting the whole search. Label each by its effect.

When space is tight, show part of the summary with an action to view all active filters. Do not silently hide restrictions. Give icon buttons accessible names that describe their actions, such as “Remove blue colour filter”, and do not rely on colour alone to show selection.

Which choices should persist?

Decide persistence by journey rather than saving every choice forever. Returning from an item should restore the working list. Starting a different task may call for different defaults.

SituationRecommended behaviour
Return from an itemRestore query, filters, sort order and list position
Reopen the filter panelShow the currently applied selections
Submit a different queryKeep visible filters unless the task requires a reset
Switch to another catalogueRemove incompatible filters and explain the change
Reopen the app laterRestore only choices intended to carry across visits
Sign out or change accountsClear account-specific search state

If a choice carries into a later visit, display it immediately. A remembered location should not quietly restrict results while the screen appears to show everything.

Avoid retaining sensitive queries merely for convenience. If recent searches are part of the design, decide what is saved, provide a removal action and keep one account’s history separate from another’s.

How should sorting differ from filtering?

Filters decide which items qualify. Sorting decides the order of qualifying items. Keep those roles separate in the interface.

Use labels that state the actual order: “Price: low to high”, “Newest first” or “Name: A–Z”. Avoid “Recommended” unless you can explain what that order means.

Choose a default for the task. A name search may start with relevance; an appointment list may start with the next available time. Show the selected order even when the person has not changed it.

Plan how equal values are ordered so items do not shuffle between requests. If sorting relies on missing information, such as distance without a selected location, ask for that information or offer another order. Do not silently substitute one.

What should happen when nothing matches?

Keep the query and filters visible. Explain that nothing matches the current combination, then offer specific recovery actions.

Separate an empty result from a failed request. “No matching items” should appear only after a successful search. A connection problem needs a retry action that preserves the person’s choices.

This worked example is illustrative:

StepPerson’s choiceExpected response
Search“Desk lamp”Show matches and retain the query
NarrowBlue and available onlyShow both active filter labels
Reach no resultsNo items matchExplain that the current combination has no matches
RecoverRemove blueKeep the query and availability filter
InspectOpen a resultShow the selected item
ReturnGo backRestore the list beside that item

Offer ways to broaden the search, such as removing one restriction or clearing filters. Do not automatically relax a condition and present the new list as an exact match. Label any suggested alternatives separately.

What should returning from a result restore?

Treat the list as a place the person left, with its own state. Preserve the query, applied filters, sort order, loaded results and scroll position.

For a long list, remember the item they opened as well as the scroll offset. If the list changes while they are away, restore them near that item where possible.

If the item disappears or no longer qualifies, retain the search choices and explain the update briefly. Avoid resetting to the top without explanation.

Test the full loop with several results: scroll, open an item, return, open another and return again. Include a slow connection and a refreshed list. Our guide on how to test an Android app before release covers planning checks beyond the successful path.

Which common mistakes should you avoid?

Check the design for these problems:

  • Hidden defaults that exclude relevant items.
  • A filter count with no readable summary.
  • Sort changes that unexpectedly remove filters.
  • A clear button whose effect is ambiguous.
  • Empty results that erase the query.
  • Failed requests presented as no matches.
  • Back navigation that restarts the list.

Not every app needs a filter panel. For a short, easily scanned list, headings or a simple search field may be sufficient. Add a control when it supports a real choice.

What questions should you settle before building?

Should filters reset when someone enters a new query?

Keep them when they still make sense, and show them clearly. If the new query changes the search scope, remove incompatible selections and explain which choices changed.

Should every filter display a result count?

Only promise counts you can keep accurate. Decide whether a count describes the current results or predicts the result after a selection. If you cannot make that meaning clear, omit it.

What belongs in the acceptance checklist?

Require visible active choices, predictable Apply and Cancel behaviour, clear sorting, useful empty and error states, and restoration after opening a result. A person should be able to explain why an item appears, change that decision and return without rebuilding their search.

Ready when you are

Planning an app of your own?

Tell us where your project is today. We will help you work out the scope before you commit to a budget.