The Explore tab (the bottom bar's search entry): ExploreFragment, module
explore_popular, reached from the feed's search tab (main_search). It
shows a search field over a grid of posts.
Wire: the enter asks for the recent searches and the search null state the
recorded tab sends; the recent request goes out while the feed is still in
front (the recording's fbsearch/recent_searches reports the feed's
endpoint, the null state reports the tab's), so the enter yields the
navigation between them. The grid itself is not requested by the tab:
the recorded app prefetches it at launch (discover/topical_explore with
is_prefetch=true; the 2026-10-23 profile-video recording) and the tab tap
in the explore recording carried no grid request at all, so the grid is the
process's launch prefetch, not this screen's data. The launch burst does not
model that prefetch yet, so the screen's data is what its own enter fetches:
the recent accounts. The tab's autoplay configs (clips/autoplay_configs/)
have no brick; the search surface's quick-promotion query is the app's, not
a request of this screen.
openSearchInput opens the search field with the recent accounts and sends
nothing (the 451 recording's field open has no request of its own).
Confirmed by the two Android 451 recordings of 2026-10-23: the first (the
feed's search tab opened, then the field) and the second (the tab, the field
and its first recent account opened into a profile).
Screenshot: none; the tab's grid shows other accounts' posts, which are not
the test accounts' to publish. The screen ships without one.
The Explore tab (the bottom bar's search entry):
ExploreFragment, moduleexplore_popular, reached from the feed's search tab (main_search). It shows a search field over a grid of posts.Wire: the enter asks for the recent searches and the search null state the recorded tab sends; the recent request goes out while the feed is still in front (the recording's
fbsearch/recent_searchesreports the feed's endpoint, the null state reports the tab's), so the enter yields the navigation between them. The grid itself is not requested by the tab: the recorded app prefetches it at launch (discover/topical_explorewithis_prefetch=true; the 2026-10-23 profile-video recording) and the tab tap in the explore recording carried no grid request at all, so the grid is the process's launch prefetch, not this screen's data. The launch burst does not model that prefetch yet, so the screen's data is what its own enter fetches: the recent accounts. The tab's autoplay configs (clips/autoplay_configs/) have no brick; the search surface's quick-promotion query is the app's, not a request of this screen.openSearchInputopens the search field with the recent accounts and sends nothing (the 451 recording's field open has no request of its own).Confirmed by the two Android 451 recordings of 2026-10-23: the first (the feed's search tab opened, then the field) and the second (the tab, the field and its first recent account opened into a profile).
Screenshot: none; the tab's grid shows other accounts' posts, which are not the test accounts' to publish. The screen ships without one.