# List View — Web app A simpler row or card layout for browsing collections where dense tabular structure is not needed. Source: https://www.checklist.design/web-app/list-view ## Items ### Primary info hierarchy The primary identifier for each item prominent enough to scan without reading every detail. _Tip: Typographic hierarchy — larger or bolder text for the primary field — is what makes lists scannable at speed._ ### Secondary metadata without clutter Supporting details — date, category, owner — present but visually subordinate. _Tip: More than 3–4 secondary fields makes rows dense and harder to scan — hiding the least important ones until hover is a reliable solution._ ### Item actions on hover Actions like edit, delete, or open appear when the user hovers over a list item. _Tip: Right-aligned actions that fade in on hover keep the list clean at rest — always-visible action icons clutter each row._ ### Bulk selection mode A way to select multiple items and act on them together. _Tip: A visible 'X items selected' bar makes it clear the user is in a different mode — without it, selection state is easy to forget._ ### Sort and filter controls Controls for ordering the list and narrowing it to specific items. _Tip: Active sort and filter state visible at all times prevents users from losing their place — a filter applied and then navigated away from should persist on return._ ### Infinite scroll or load more A way to see additional items beyond the initial load. _Tip: 'Load more' is generally preferable to infinite scroll for content users need to reference — it preserves scroll position and lets users find where they left off._ ### Group or section headers Visual dividers and labels when items are organised into categories or time buckets. _Tip: Sticky group headers make it easier to navigate long lists — the user always knows which group they are in._ ### Empty and first-use states Helpful messages and actions when there are no items to display. _Tip: A blank list with no guidance is a top drop-off point for new users — first-use empty states that link directly to creating the first item consistently improve activation._ ## License for the Checklist Design collection Checklist Design collection: https://github.com/Checklist-Design/skills Snapshot: bfae71e507b1b7c03c12e0756402b60eb80f5d14 · Imported: 2026-11-12 Republished under the MIT License. Original checklist text belongs to Checklist Design. MIT License Copyright (c) 2026 Checklist Design Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.