in a readable way. • Often, allowing users to drill into rows or perform actions on them. • Preserving relationships between items when there’s not enough space to show everything. Current UI pattern
subset of results so we don’t have to load everything at once. • Keeping users engaged in the content, without the distractions of navigation. • Easy for reading New approach
chronological order Dominant action scan, compare Read, scroll Screen real estate Less ✓ More X Easy digestible No X Yes ✓ Mobile No X Yes ✓ Scannability Yes ✓ Yes ✓ Readability No X Yes ✓ UI comparison
the problem, which means think about the users • Understand what pattern is best suited for, what their pros and cons are • Do usability testing with user • Be confident in the choices Summary
vs List group Checkbox vs Toggle Tags vs Badges Breadcrumb vs Tree view Select vs Radio buttons Accordion vs Tabs Spinner vs Progress bar Which UI pattern should I use?
one, or multiple options from a list of items. The user has to perform extra steps for changes to be effective. For example, user must click a "submit" to apply changes. Radio buttons Should be used when the user can select one, and only one, option from a list of items, all options permanently visible so that users can easily compare them. Toggles Should be used to represent an action, like turning something on or off, the changes become effective immediately after the user changes them. Checkbox vs Toggle vs Radio