Recommendation Feed

Personalized ranked feed with explanations, relevance feedback, dismiss actions, and fallback content. The screen connects For you and Following so product teams can find the “Tune feed” action while checking recommendations and high relevance.

Use this reference when you need to design this workflow inside an existing product. The example includes practical records such as Permission design patterns and Analytics workflows for SaaS, rather than an empty visual shell.

Recommendation Feed
Use this template in Figr

Template facts

Screen

Workspace

Primary action

Tune feed

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 “Tune feed” action without losing sight of recommendations, high relevance and the affected records. Keep the decision and its outcome clear before moving to the next task.

Key elements

  • Primary action: Tune feed is clearly available where the task happens.
  • Main view: For you keeps the starting point obvious.
  • Connected view: Following supplies nearby context.
  • Metric: Recommendations is visible with a meaningful value.
  • Another signal: High relevance helps people judge what to do next.
  • Representative record: Permission design patterns makes the example specific.
  • Second record: Analytics workflows for SaaS 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 for you without changing the layout unexpectedly.
  • Unavailable or restricted panel; explain the problem and preserve work.
  • Permission denied for following; clarify who can continue.
  • Success after choosing Tune feed; 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

For you → Following → Tune feed → Review outcome

Patterns used

Workspace, For you, Following, Saved, 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 Permission design patterns with Analytics workflows for SaaS. Make recommendations clear, then use high relevance 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 “Tune feed” action. The happy path alone is not enough.

Related UI examples: Browse Categories, Recent Items, Command Palette.

Start from this in Figr

Design a recommendation feed screen for our existing software product. Use our real design-system tokens, components and product language. Show For you and Following, include believable records such as Permission design patterns, and make tune feed easy to find. Map loading, empty, failure, permission and success states before you create editable high-fidelity screens.

Open Figr