Find tab: invert flow — show results first, filters on demand #132

Closed
opened 2026-05-11 11:31:08 -07:00 by pyr0ball · 0 comments
Owner

Problem

The Find tab currently leads with an empty-state form that requires user action before showing any results. For users with ADHD or decision fatigue, a blank form is a stopping point. Showing results immediately and treating filters as optional refinements reduces the activation energy to start.

Proposed approach

  • On Find tab load, fire a default suggestion using current pantry (same as the main suggest button)
  • Show results immediately in the recipe grid
  • Collapse filters into a "Refine" disclosure panel (open by default on first visit, collapsed thereafter)
  • Filter changes re-run the suggestion live
  • If pantry is empty, show the empty pantry prompt rather than a blank form

Acceptance criteria

  • Results visible on tab open without any user action required
  • Filter panel collapsible, state persisted to localStorage
  • No regression on existing filter behaviour

From

kiwi UX audit (2026-05-11) — cf-a11y longer-term #1

## Problem The Find tab currently leads with an empty-state form that requires user action before showing any results. For users with ADHD or decision fatigue, a blank form is a stopping point. Showing results immediately and treating filters as optional refinements reduces the activation energy to start. ## Proposed approach - On Find tab load, fire a default suggestion using current pantry (same as the main suggest button) - Show results immediately in the recipe grid - Collapse filters into a "Refine" disclosure panel (open by default on first visit, collapsed thereafter) - Filter changes re-run the suggestion live - If pantry is empty, show the empty pantry prompt rather than a blank form ## Acceptance criteria - Results visible on tab open without any user action required - Filter panel collapsible, state persisted to localStorage - No regression on existing filter behaviour ## From kiwi UX audit (2026-05-11) — cf-a11y longer-term #1
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: Circuit-Forge/kiwi#132
No description provided.