Repository navigation
Mobile search and history #25
Description
Part of #14 (W3 — mobile v1). Blocked by files slice; paging helper putdotio/putio-sdk-kotlin#22 recommended.
Outcome
Search and history complete the "find it again" loop on mobile.
Scope
- Search: keyword search with debounce, paged results, recent searches (using Android-owned keys in OAuth-app-scoped
/config) — feat(mobile): add search and history #72 (SearchControllerdebounce, paged results, recent-search terms with malformed-term rejection) - History: paged event list grouped by date, event-type rendering (shared file vs transfer), navigate to file, clear-all with confirm, gated by account-wide
history_enabledfrom/account/settings— feat(mobile): add search and history #72 plus fix(settings): sync history availability #102 (live off/on/save proof of thehistory_enabledgate) - Empty/error/loading states per contract — feat(mobile): add search and history #72; disabled-history copy asserted in fix(settings): sync history availability #102
Ownership contract
/configis scoped to the OAuth app. Android owns its config keys, parsing, and defaults; shared SDKs expose only the generic JSON boundary./account/settingsis account-wide across apps.- File/folder sort uses
/files/set-sort-by, separate from both.
Acceptance criteria
- DoD: verify green; screen recording of search → open result and history → clear flows attached
Activity
altaywtf commentedon Aug 30, 2026
#72 implements Search and History and includes both required behavior captures.
Its Android CI failure is dependency drift, not an app regression: CI checks the Kotlin SDK
main, which does not yet expose the genericappConfigJSON boundary. putio-sdk-kotlin#30 is green and clean-reviewed. Once SDK #30 lands, rerun #72; #72 then closes this issue.