| UI or UX | UI + UX - Automatic list of items the current user opened recently | UI + UX - Curated onward links connected to the current content | UI + UX - Hierarchy orientation navigation |
| UI guidance | Render a labelled list or rail of items the current user actually opened, ordered most recent first, with enough identity to recognize each item such as name, type, thumbnail or icon, location, status, and last-viewed time. | Render a short, labelled collection of links whose destinations are closely related to the current content, using destination-specific link text and optional relation labels such as service, guidance, external, or PDF. | Render a labeled breadcrumb nav as an ordered hierarchy from the broadest relevant ancestor to the current page, with real ancestor links and a distinct current-page item. |
| UX guidance | Use recently viewed to reduce re-finding effort when users compare items, pause work, resume documents, or return to records they inspected during the current or recent sessions. | Use related links to support users who have finished or understood the current content and need a relevant next page, adjacent service, reference, or follow-up resource. | Orient users who arrive deep in a site by exposing the canonical parent-child relationship for the current page. |
| Good UI | A procurement dashboard shows Recently viewed records with title, record type, status, project, last-viewed time, and a remove control for each row. | A benefits guidance page ends with Related links: Check eligibility for support, Upload evidence for your claim, and Appeal a support decision, each with a concise relation label. | Home, Projects, Migration, and Runbook appear in hierarchy order with ancestor links and Runbook marked current. |
| Bad UI | A homepage shows a Recently viewed carousel filled with promoted products the user never opened. | A page ends with More information containing Home, Contact us, Apply now, Old 2018 guidance, Help, and an unrelated account settings link. | Recent clicks are displayed as if they were the page hierarchy. |
| Good UX | A user opens several supplier records, returns to the dashboard, and reopens the most recent record without reconstructing the search. | A user reads claim renewal guidance, chooses Upload evidence for your claim, and sees why that destination is the next useful service page. | Opening a saved deep link still shows the same parent path and lets users jump to Migration or Projects. |
| Bad UX | Users trust a Recently viewed rail as a recommendation and choose an irrelevant item because sponsored content was mixed into history. | Users follow a generic More information link and land on an unrelated policy collection. | The breadcrumb changes after every click, so the same page shows different trails for different users. |
| Best fit | Users inspect multiple objects and often need to return to one they recently opened. | The current page has a few genuinely adjacent pages, services, programs, or resources users often need next. | Pages sit inside a clear parent-child hierarchy. |
| Avoid when | The content set is tiny, linear, or easy to scan without history. | Links are only loosely associated by topic tags or organizational ownership. | The app has a flat structure with no meaningful parent levels. |
| Required state | Empty or hidden state before any qualifying item has been viewed. | Default state with a labelled, curated related-links block and descriptive link text. | Interior page with full ancestor trail. |
| Accessibility burden | Use a heading or labelled region that describes the scope of the list. | Use descriptive link text that makes sense out of context. | Place the trail in a labeled nav element. |
| Common misuse | Filling recently viewed with recommendations, ads, popular items, or related content. | Using related links as a catch-all further-reading dump. | Showing browsing history instead of hierarchy. |