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 sends the playback configuration (clips/autoplay_configs/) at
once, waits the app's own fragment settle, then asks for the recent searches,
the search null state and — when the process's stash holds no fresh answer
for the tab's surfaces — the search surface's quick promotions, as the
the app's tab does; the fragment's requests go out while the tab is still
coming to front and the navigation commits while their answers are in
flight (the recordings split each of them across the commit, so the
transition's race window accepts either side, the scene's recording
deciding). When the account's popular-keyword cache is more
than a day old the tab also refreshes it, right after the configuration — a
fact of its own, which neither of the two lists below reads. Two decisions
decide those lists (see explore.process-facts.ts): the search field's
suggested-user sections (discover/sectioned_ayml/, sent twice) load when
the account's MobileConfig turns them on (ReadMobileConfig, the app's
alternative-pair read), and the Explore grid
(discover/topical_explore/, is_prefetch=false) loads on such a tab only
when the process does not already hold it — the launch's prefetch
(getTopicalExplore, is_prefetch=true) answered. The
tab's quick-promotion slot (EXPLORE) fires
its four screen-load triggers once the fragment is loaded — after the
autoplay configuration, which the app sends without them — and they run
over the fragment's requests and the slot's batch, so the recent searches and
the null state carry 332008142,332009826,332019700,332020325 exactly as
the app's do; a tab whose process already answered the slot's surfaces sends
no batch and its flows run over the fragment's requests alone. The screen's
own data is the recent accounts.
openSearchInput opens the search field with the recent accounts and sends
nothing (the 451 app's field open has no request of its own).
Confirmed on Android 451: the feed's search tab opened, then the field; and
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 sends the playback configuration (
clips/autoplay_configs/) at once, waits the app's own fragment settle, then asks for the recent searches, the search null state and — when the process's stash holds no fresh answer for the tab's surfaces — the search surface's quick promotions, as the the app's tab does; the fragment's requests go out while the tab is still coming to front and the navigation commits while their answers are in flight (the recordings split each of them across the commit, so the transition's race window accepts either side, the scene's recording deciding). When the account's popular-keyword cache is more than a day old the tab also refreshes it, right after the configuration — a fact of its own, which neither of the two lists below reads. Two decisions decide those lists (seeexplore.process-facts.ts): the search field's suggested-user sections (discover/sectioned_ayml/, sent twice) load when the account's MobileConfig turns them on (ReadMobileConfig, the app's alternative-pair read), and the Explore grid (discover/topical_explore/,is_prefetch=false) loads on such a tab only when the process does not already hold it — the launch's prefetch (getTopicalExplore,is_prefetch=true) answered. The tab's quick-promotion slot (EXPLORE) fires its four screen-load triggers once the fragment is loaded — after the autoplay configuration, which the app sends without them — and they run over the fragment's requests and the slot's batch, so the recent searches and the null state carry332008142,332009826,332019700,332020325exactly as the app's do; a tab whose process already answered the slot's surfaces sends no batch and its flows run over the fragment's requests alone. The screen's own data is the recent accounts.openSearchInputopens the search field with the recent accounts and sends nothing (the 451 app's field open has no request of its own).Confirmed on Android 451: the feed's search tab opened, then the field; and 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.
Guide: Explore tab