What’s here
A pattern is a common way to solve an interface design problem. It can describe a single control, a page layout, or how an interface responds to someone. A product is an app people can use. A capture is a dated screenshot, with notes pointing out the patterns it shows.
Each pattern has its own page. You can also browse screenshots by product, industry, or dashboard type. Those browsing pages are built automatically from the screenshot records.
How patterns are grouped
Eight of the nine dashboard groups come from Bach et al., Dashboard Design Patterns (IEEE VIS 2023). This peer-reviewed research is a useful starting point for understanding dashboard design.
This site adds a ninth group, Dashboard features, with ten patterns for everyday app needs. These cover filters and time-range pickers, as well as empty, loading, and error states. The group also includes tools for building and sharing dashboards and setting alerts.
Patterns and screenshots use a fixed set of categories. New categories are added to that shared list so the labels stay consistent across the site.
How entries are written
Each entry starts with the problem and a suggested solution. It explains when to use the pattern, when to avoid it, and its trade-offs. A checklist helps you review your design. Comparisons, related patterns, and sources give you more to explore. Product examples come from live demos, with screenshots taken at twice the display resolution. Captions explain how each product uses the pattern and what makes its approach different.
Screenshots show a product at a particular time. A screenshot from September 2026 may look different from the product today. There is no set policy yet for replacing older screenshots after a redesign.
Screenshots and fair use
Screenshots are used for commentary and criticism. Each one includes a date, a link to the product, and the version number when it was visible. Logos and branding stay in the image so it is clear whose work is shown.
If you own work shown here, you can ask to have a screenshot removed or updated.
For AI tools
The llms.txt file lists every pattern. Each pattern also has a
Markdown version at /<library>/<slug>.md for AI tools to read.
Both include other names for the pattern. For example, a KPI tile is also called a
stat card, big number, BAN, or metric card. These names help tools find the same
pattern under different terms.