Recents and frequents are a path besides search

What it is

Much retrieval needs no query: people want “the one from a moment ago,” “the one I open every Monday.” Recents and frequents are a second path beside the search box, listing tappable objects by time or by rate. They cover known-item, short-interval locate—not save-for-later pins, and not keyword exploration of the library. Without this path, people use search as a history log and toss a half-remembered title into the box.

Why it happens

Working memory keeps what was just done, not an exact title. A recents list picks “the object from a few minutes ago” out of that memory at the cost of one scan. Frequents capture a stable habit that recency cannot: last week’s unopened weekly report should still sit there. Search-only products make people type fuzzy words, fail, and blame coverage. If recents are polluted by autosynced previews, background indexers, or files someone else opened, the list is no longer “what I just did,” and the cue breaks. Frequents counted on global clicks rather than “I opened” dump org-hot items onto a person, and the path fails again. The path must still exist when search fails: recents beside an empty result is a detour, not abandonment.

Studying it

The main job is to open “what you viewed ten minutes ago” and “what you use every week,” with no hint to search or to use a list. Compare search-only, recents, recents plus frequents.

Independent variables: whether recents count only one’s own opens, whether previews and others’ opens are excluded, the window for frequents. Dependent variables: retrieval without typing, others’ files mistaken as one’s own, search used as history.

A lab gap that is too short leaves the title in the mouth. Insert an unrelated task. Do not count a saved-list item as recents success—that is another memory.

Where it stops holding

On a public terminal or a shared account, recents leak privacy and should be off or behind unlock. Heavy read-only browsing (review queues) turns recents into noise; offer “don’t remember this open.” A new account has no frequents; the empty state should say they appear after repeated opens, not fill with org recommendations posing as frequents. When recents do not sync across devices, say “this device only,” or the other machine looks like it lost files.

Applying it

• Put Recently opened on the locate entry. Count only objects the person opened on purpose; exclude flash previews and others’ activity.
• Add Frequents by personal open rate, not library-wide heat.
• Keep a path to recents and frequents beside empty search results.
• Verify: after opening several items and doing something unrelated, ask for a named one. Note whether they used recents instead of typing the title. A file someone else opened should not appear on their recents.

Related

• Within the group: H8.13.1 Search must say whether it covers title, body, or metadata · H8.13.3 Empty results need causes other than a narrow query · H8.13.4 Near-duplicate names need extra cues to tell them apart
• Adjacent: H8.05 Save for Later · G3.11 Search History · H8.14 Content Lifecycle and Archiving
• Search terms: recents · frequents · known-item finding