Browse Categories

Browse a large product catalog through categories, curated collections, trending items, and scoped filters. The screen connects Categories and Featured so product teams can find the “View collections” action while checking categories and collections.

Use this reference when you need to design this workflow inside an existing product. The example includes practical records such as Revenue & finance and Collaboration & docs, rather than an empty visual shell.

Use this template in Figr

Template facts

Screen

Primary action

View collections

Pattern

State

Default, loading, empty, error, permission, success

Design system

Adaptable product UI theme

What this screen helps users do

Product teams need a clear “View collections” action without losing sight of categories, collections and the affected records. Keep the decision and its outcome clear before moving to the next task.

Key elements

Primary action: View collections is clearly available where the task happens.
Main view: Categories keeps the starting point obvious.
Connected view: Featured supplies nearby context.
Metric: Categories is visible with a meaningful value.
Another signal: Collections helps people judge what to do next.
Representative record: Revenue & finance makes the example specific.
Second record: Collaboration & docs shows the pattern works beyond one item.

States worth designing

No matching records; show what people can do instead of leaving a blank panel.
Loading categories without changing the layout unexpectedly.
Search or filter request failed; explain the problem and preserve work.
Permission denied for featured; clarify who can continue.
Success after choosing View collections; confirm the result and the next step.
Network or data refresh failure; offer a retry without losing context.

Where this screen sits in the flow

Categories → Featured → View collections → Review outcome

Patterns used

Search, Categories, Featured, Trending, accessible states, contextual actions

Why these choices work

Preserve the query and chosen filters as people inspect results. Make no-results recovery useful instead of a dead end.

In this design, people should be able to compare Revenue & finance with Collaboration & docs. Make categories clear, then use collections to explain whether the next step needs attention.

Before handing this to a designer or engineer, check keyboard focus, error copy, permissions and what happens after they choose the “View collections” action. The happy path alone is not enough.

Related UI examples: Command Palette, Recommendation Feed, Saved Searches.

Start from this in Figr

Design a browse categories screen for our existing software product. Use our real design-system tokens, components and product language. Show Categories and Featured, include believable records such as Revenue & finance, and make view collections easy to find. Map loading, empty, failure, permission and success states before you create editable high-fidelity screens.

Open Figr