Description

Rollout / safety net

• Feature flag explorePageV2Enabled (app/selectors/featureFlagController/explorePageV2/index.ts): defaults to false. When off, users get the legacy single-page Explore in ExplorePageV1.tsx (one scroll: Quick Actions, predictions, tokens, perps, stocks, sites). When on, they get the tabbed Explore V2—ops can switch back to V1 via the flag without reverting code.

Main additions

• Tabbed Explore (V2) in TrendingView.tsx using TabsList: Now, Macro, RWAs, Crypto, Sports, and Dapps—each tab is its own focused vertical experience instead of one long mixed feed.
• Six tab screens under app/components/Views/TrendingView/tabs/ that split content by theme (e.g. Macro uses macro-style perps + predictions; Crypto emphasizes crypto perps/tokens; Sports uses sports-oriented prediction markets via useSportsMarketsFeed).
• Richer presentation: pill carousels and toggles (PillScrollList, PillToggleCardList, ExplorePill, perps/token pill row items) so movers and macro views are easier to scan than the old single-stack layout alone.
• Dapps tab adds browser-grounded sections: recents, favorites, and networks (new feeds/dapps/ hooks and tile/list UI) plus trending sites, wired through Sites / UrlAutocomplete / SitesFullView and hooks like useBrowserFavoritesSites and useBrowserRecentsSites.
• Perps feeds are tab-aware: usePerpsFeed supports variants (all / macro / crypto, etc.) so each tab can show the right subset with row vs tile vs pill layouts as needed.
• Explore search rework under app/components/Views/TrendingView/search/ (useExploreSearch, ExploreSearchResults, SearchFeedRow, TapView, search analytics)—multi-feed omni-search with debouncing and clearer section typing for renderers.
• Supporting infra: feature-flag registry for tests, new i18n strings, navigation type updates where Explore touches routes, and TabsBar tweaks for the new tab strip.

Main removals / replacements

• Removed the “sections config” architecture: sections.config.tsx (and tests) that drove dynamic section composition is gone in favor of explicit tab components.
• Removed exploreSectionsOrder feature-flag plumbing—remote ordering of Explore sections is no longer the model with fixed tabs on V2 (V1 keeps a fixed legacy stack in ExplorePageV1).
• Removed / replaced older Explore search helpers: utils/exploreSearch and the hooks-local useExploreSearch in favor of the search/ module and a single consolidated hook API.

What stayed the same (high level)

• Core feeds (tokens, stocks, predictions, sites, perps) remain the building blocks; they are recomposed per tab with new filters/UI where needed—not entirely new domains everywhere.
• V1 behavior stays available behind the flag for rollback and gradual rollout.

Changelog

CHANGELOG entry: developed explore page v2 behind a FF

Related issues

Fixes: https://consensyssoftware.atlassian.net/browse/ASSETS-3088

Manual testing steps

Feature: my feature name

  Scenario: user [verb for user action]
    Given [describe expected initial app state]

    When user [verb for user action]
    Then [describe expected outcome]

Screenshots/Recordings

Before

After

s] -->

Pre-merge author checklist

• I've followed MetaMask Contributor Docs and MetaMask Mobile Coding Standards.
• I've completed the PR template to the best of my ability
• I've included tests if applicable
• I've documented my code using JSDoc format if applicable
• I've applied the right labels on the PR (see labeling guidelines). Not required for external contributors.

Performance checks (if applicable)

• I've tested on Android
  • Ideally on a mid-range device; emulator is acceptable
• I've tested with a power user scenario
  • Use these power-user SRPs to import wallets with many accounts and tokens
• I've instrumented key operations with Sentry traces for production performance metrics
  • See trace() for usage and addToken for an example

For performance guidelines and tooling, see the Performance Guide.

Pre-merge reviewer checklist

• I've manually tested the PR (e.g. pull and build branch, run the app, test code being changed).
• I confirm that this PR addresses all acceptance criteria described in the ticket it closes and includes the necessary testing evidence such as recordings and or screenshots.