Smart-home devices often serve multiple users with different needs and preferences. Designing for shared use can reduce unnecessary friction and dependency.
iOS 26’s visual language obscures content instead of letting it take the spotlight. New (but not always better) design patterns replace established conventions.
Two types of foldable smartphones blur the boundaries between traditional device sizes. Fold-out and flip phones create new viewports that hint at future smartphones.
Maximize the value of your smartwatch notifications by making them personally relevant, appropriately timed, non-repetitive, and sufficiently informative.
Breakpoints determine when a webpage may adjust to different layouts. They help designers (and developers) maintain layout consistency across multiple screen sizes, orientations, and devices.
Tables of contents show mobile users an overview of the information on the page and allow them to easily access the piece of content that is relevant to them. Two possible implementations involve in-page links and accordions.
Applications native to smartwatch operating systems get used the most. Just because a new smartwatch app could offer basic functionality, it does not mean that users will find it valuable.
Smartwatches are for more than just receiving notifications and tracking steps. They afford at least 6 different types of interactions that users find useful.
Decorative images should not be used on mobile, as they lengthen the page and make it load more slowly. Use images only if they add informational value to your page.
Mobile-first web designs cause significant usability issues when viewed on desktop. Content becomes overly dispersed across long scrolling pages with expansive white space and enlarged images and fonts, making it difficult for users to consume and understand the information.
Accordions provide an overview of the whole page and mitigate the problem of long mobile pages, allowing users to directly access the content of interest.
Dark mode is popular, but not always a critical feature. Users behave similarly without it. They think about it at the system level, not the application level.
