Skip to main content

Search UI Design: Suggestions, Filters and Results

Search UI design for mobile apps: entry points, recent and trending states, autocomplete, filter chips and sheets, result layouts and no-results recovery.

Insights10 min read1,839 words

This guide is for designers, PMs and founders working on any app where people look for things: products, recipes, places, messages, files or people. Search is often the highest-intent moment in an app, and small design decisions decide whether it ends in a result or an exit. You will get the full anatomy of mobile search, specs for each state, filter patterns and a checklist.

TL;DR: Design search as five states: entry, pre-search (recents and suggestions), typing (autocomplete), results (with filters and sort) and no results. Make the search field obvious, show helpful content before typing, suggest as people type, tolerate typos, put the most-used filters in chips with the rest in a sheet, and never end on a blank screen.

The five states of search UI design

StateWhat the user is doingWhat the screen should offer
EntryDeciding to searchA visible search field or tab
Pre-searchField focused, nothing typedRecent searches, trending, categories
TypingEntering a queryAutocomplete suggestions, instant matches
ResultsScanningClear result list or grid, filters, sort, count
No resultsStuckCorrections, relaxed filters, alternatives

Most search problems come from designing only the results state. The other four decide whether people get there.

1. Entry points: make search easy to find

How prominent search should be depends on how central it is to your app.

PatternWhen to useExamples
Persistent search field at the top of homeSearch is the main way to navigateMarketplaces, maps, music apps
Dedicated Search tabSearch plus browsing is a core activitySpotify's Search tab, App Store's Search tab
Search field in the navigation bar of a listSearching within one listMail, Notes, Settings
Search icon that expandsSearch is occasionalUtility and content apps with little to search

Rules:

  • •Label the field with what can be searched: "Search recipes, ingredients" beats "Search."
  • •On iOS, the system search field sits in or below the navigation bar and can hide on scroll; on Android, Material 3's search bar is a full-rounded field that expands into a full-screen search view on phones.
  • •Keep the tap target at least 44 pt (iOS) or 48 dp (Android), and make the entire field tappable, not just the icon.

For platform specifics, see our iOS Human Interface Guidelines summary and Material Design 3 guide.

2. Pre-search: never show an empty screen

When the field is focused and empty, the screen is prime real estate. Useful content, in priority order:

  1. •Recent searches, most recent first, each removable, with "Clear all." Limit to around five to eight.
  2. •Trending or popular searches for discovery, especially for new users with no history.
  3. •Categories or shortcuts for browsing: genres, departments, cuisines.
  4. •Recently viewed items, which often beat recent queries for return visits.

Airbnb's search starts with structured questions (where, when, who) instead of a free text box, because its queries share the same three dimensions. If your queries are structured, consider guided search the same way.

3. Typing: autocomplete that helps

Autocomplete reduces typing, prevents misspellings and teaches users what exists.

Types of suggestions

Suggestion typeWhat it showsBest for
Query suggestionsCompleted search phrasesLarge catalogs, content
Scoped suggestions"Shoes in Women's"Catalogs with clear categories
Instant resultsActual items with thumbnailsSmall catalogs, contacts, files
MixedQueries, categories and top items groupedMarketplaces, super apps

Autocomplete specs

  • •Start suggesting after one or two characters, with a short debounce so the list does not flicker.
  • •Show up to about 6 to 10 suggestions above the keyboard; the keyboard covers a large share of the screen, so the top suggestions matter most.
  • •Highlight the predicted part, not the typed part. Making the completion bold (and the typed text regular) helps people scan for differences.
  • •Row height of at least 44 pt / 48 dp, with a leading icon distinguishing type (clock for recent, magnifier for query, thumbnail for item).
  • •Add an "insert" arrow on query suggestions so users can fill the field and keep refining without searching.
  • •Tolerate typos: match "chiken" to "chicken" and handle plurals and synonyms.

Keyboard behavior

  • •Set the return key to "Search."
  • •Dismiss the keyboard when the user scrolls the results.
  • •Keep a clear button inside the field and a "Cancel" action on iOS to exit search.
  • •Preserve the query when users go to a result and come back.

4. Results: scannable, filterable, sortable

Layout

Content typeLayout
Products, recipes, photosTwo-column grid with image, title, key attribute
PlacesMap and list toggle, or a list sheet over a map
Messages, files, settingsSingle-column list with highlighted matching text
Mixed typesGrouped sections with "See all" per group, or type tabs

Show the result count and the active query at the top. Highlight matching terms in text results so people see why each result appeared.

Filters

Filters are where many mobile search experiences break. A pattern that works:

  1. •Filter chips in a horizontal row above results for the three to six most-used filters (price, rating, distance, "open now").
  2. •A "Filters" button with a badge showing how many filters are active, opening a full sheet with every filter.
  3. •Live counts in the sheet button: "Show 128 results," updated as filters change.
  4. •Applied filters visible as removable chips on the results screen.
  5. •"Clear all" in the sheet and when filters lead to zero results.
Filter typeControl
Single choiceRadio list or segmented control
Multiple choiceCheckboxes or multi-select chips
RangeDual-thumb slider with editable min and max fields
Yes/noSwitch
Long lists (brands)Searchable list within the sheet

Sort

Put sort in its own control, separate from filters, with a clear default label such as "Sort: Relevance." Offer only the sort orders people use: relevance, price, rating, distance, newest.

5. No results: always offer a way forward

A zero-results page is a dead end unless you design it as recovery:

  • •Repeat the query: "No results for 'blu sneekers'."
  • •Offer a correction: "Did you mean 'blue sneakers'?" or run it automatically and say so.
  • •Suggest removing the most restrictive filter, as a one-tap chip.
  • •Show related categories or popular items.
  • •Offer to notify the user or save the search, where relevant.

Our empty state design guide covers copy and layout for these screens in more depth.

Advanced patterns

  • •Scoped search: let users search within a section (this playlist, this folder) with a visible scope label and a way to widen it.
  • •Voice and camera search: a microphone or camera icon inside the field for apps where speaking or photographing is easier than typing, such as shopping or plant identification.
  • •Saved searches and alerts: for marketplaces and property apps where inventory changes.
  • •Search within results: refine with additional keywords without losing filters.

In shopping apps, search connects directly to product pages and checkout, so mapping the whole journey matters; see our e-commerce user flow and mobile checkout design guides.

Worked example: search in a grocery app

  1. •Entry: persistent field on Home, "Search groceries and recipes."
  2. •Pre-search: recent searches (oat milk, bananas), "Popular this week" chips, aisle shortcuts.
  3. •Typing "avo": suggestions "avocado," "avocado oil," "avocados, ripe & ready," plus two instant product results with prices and add buttons.
  4. •Results for "avocado": two-column grid with price, size, add button; chips for Organic, On offer, Under $5; Filters button with badge; "Sort: Relevance."
  5. •No results for "avocardo": auto-corrected to "avocado" with a "Search instead for 'avocardo'" link.

Adding items directly from suggestions shortens the path from intent to cart. You can generate a first draft of each of these search states in floow and compare layouts before building.

Search UI design checklist

  • • Search field is visible where search matters, labeled with what can be searched
  • • Pre-search state shows recents, trending and categories
  • • Recents are removable individually and in bulk
  • • Autocomplete starts early, highlights the completion and tolerates typos
  • • Suggestion rows meet minimum tap sizes with type icons
  • • Return key says "Search"; keyboard dismisses on scroll
  • • Results show the count and highlight matches
  • • Top filters as chips, all filters in a sheet with live result counts
  • • Applied filters visible and removable
  • • Sort separate from filters, with a clear default
  • • No-results state offers corrections and relaxed filters
  • • Query and scroll position preserved when returning from a result
  • • Loading state shown before results, never an early "no results"

FAQ

Where should the search bar go in a mobile app?

At the top of the screen where search is the main activity, either as a persistent field on the home screen or in a dedicated Search tab. For searching within a single list, place it in or under that screen's navigation bar.

How many autocomplete suggestions should I show?

Around six to ten works on most phones, because the keyboard covers much of the screen. Prioritize the most likely completions at the top and mix in item results if your catalog is small.

Should filters be chips or a separate screen?

Both. Show the few most-used filters as chips for quick access, and put the full set in a bottom sheet or full-screen panel with a live result count on the apply button.

What should a no-results page show?

The query, a spelling correction if one exists, a way to remove restrictive filters, and alternatives such as related categories or popular items. Never leave users on a blank screen.

Design it with floow

Design every search state for your app in floow and refine the layouts in chat. Start with:

Design 4 search screens for an iOS grocery app: pre-search with recent searches and popular chips, autocomplete while typing "avo" with product thumbnails and add buttons, a two-column results grid with filter chips and a Filters button badge, and a filters bottom sheet with price range slider and "Show 128 results" button.

Design your mobile app with AI.

Generate pixel-perfect iOS and Android screens in seconds, then export to Figma or code.