Favorites & Collections

Organize saved products, documents, and research into named collections that stay easy to revisit and share. The screen connects Favorites and Collections so product teams can find the “New collection” action while checking saved items and collections.

Use this reference when you need to design this workflow inside an existing product. The example includes practical records such as Enterprise design references and AI onboarding patterns, rather than an empty visual shell.

Favorites & Collections

Template facts

Screen

Workspace

Primary action

New collection

Pattern

Workspace

State

Default, loading, empty, error, permission, success

Design system

Adaptable product UI theme

What this screen helps users do

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

Key elements

  • Primary action: New collection is clearly available where the task happens.
  • Main view: Favorites keeps the starting point obvious.
  • Connected view: Collections supplies nearby context.
  • Metric: Saved items is visible with a meaningful value.
  • Another signal: Collections helps people judge what to do next.
  • Representative record: Enterprise design references makes the example specific.
  • Second record: AI onboarding patterns shows the pattern works beyond one item.

States worth designing

  • First-use workspace; show what people can do instead of leaving a blank panel.
  • Loading favorites without changing the layout unexpectedly.
  • Unavailable or restricted panel; explain the problem and preserve work.
  • Permission denied for collections; clarify who can continue.
  • Success after choosing New collection; 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

Favorites → Collections → New collection → Review outcome

Patterns used

Workspace, Favorites, Collections, Shared, accessible states, contextual actions

Why these choices work

Keep the main job visible above supporting panels. Group related controls and surface exceptions where people act.

In this design, people should be able to compare Enterprise design references with AI onboarding patterns. Make saved items 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 “New collection” action. The happy path alone is not enough.

Related UI examples: Recent Items, Compare Items, Recommendation Feed.

Start from this in Figr

Design a favorites & collections screen for our existing software product. Use our real design-system tokens, components and product language. Show Favorites and Collections, include believable records such as Enterprise design references, and make new collection easy to find. Map loading, empty, failure, permission and success states before you create editable high-fidelity screens.

Open Figr