Skip to content

Add the Explore tab screen - #117

Open
AndrewG828 wants to merge 1 commit into
user/andrewgao/feature/UI-UX-Lucid-Refactor-06-explore-sectionsfrom
user/andrewgao/feature/UI-UX-Lucid-Refactor-07-explore-tab
Open

Add the Explore tab screen#117
AndrewG828 wants to merge 1 commit into
user/andrewgao/feature/UI-UX-Lucid-Refactor-06-explore-sectionsfrom
user/andrewgao/feature/UI-UX-Lucid-Refactor-07-explore-tab

Conversation

@AndrewG828

@AndrewG828 AndrewG828 commented Sep 3, 2026

Copy link
Copy Markdown
Member

Stacked PR 7 of 15. Based on #116 — merge in order.
#111#112#113#114#115#116#117#118#119#120#121#122#123#124#125

Assembles the discovery sections into a tab root: category shortcuts, a Just
For You row fronting Saved and Recently Viewed, then Daily Picks and Trending.
It is not in the tab bar yet — that comes with the navigation rework.

Explore owns a local SearchViewModel rather than the shared singleton.
Both tab roots stay mounted under the new navigation, so sharing one would mean
typing in Explore silently replaced Home's results.

SearchPanel (new) is the expanded search card, extracted rather than written
inline: Home and the category browser present the identical card, and this is
the first of the three to land. Keeping it in one place also keeps the "opaque,
not glass" decision in one place — materializing a glass layer that large in
the same frame the keyboard animates made opening search feel like a hang.

Scrolling is disabled only while the card covers the feed with no results yet.
Gating it on "is the panel open" instead — which is what the first cut did —
also freezes the search results the panel hands back, leaving you unable to
scroll past the first four.

Co-Authored-By: Claude Opus 5 (1M context) noreply@anthropic.com
Claude-Session: https://claude.ai/code/session_017R8mua9xepzF3mnRETtd6W

Assembles the discovery sections into a tab root: category shortcuts, a Just
For You row fronting Saved and Recently Viewed, then Daily Picks and Trending.
It is not in the tab bar yet — that comes with the navigation rework.

Explore owns a local `SearchViewModel` rather than the shared singleton.
Both tab roots stay mounted under the new navigation, so sharing one would mean
typing in Explore silently replaced Home's results.

`SearchPanel` (new) is the expanded search card, extracted rather than written
inline: Home and the category browser present the identical card, and this is
the first of the three to land. Keeping it in one place also keeps the "opaque,
not glass" decision in one place — materializing a glass layer that large in
the same frame the keyboard animates made opening search feel like a hang.

Scrolling is disabled only while the card covers the feed with no results yet.
Gating it on "is the panel open" instead — which is what the first cut did —
also freezes the search results the panel hands back, leaving you unable to
scroll past the first four.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_017R8mua9xepzF3mnRETtd6W
@coderabbitai

coderabbitai Bot commented Sep 3, 2026

Copy link
Copy Markdown

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Team

Run ID: 26e351f1-b310-4166-a48c-95a374497286

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • 🔍 Trigger review

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant