Many apps today, such as Google Now, Spotify and Amazon, make assumptions about user preferences based on personal data. They may even use this information to make decisions on our behalf, without any direct input from us. For example, Facebook tailors your news feed and Amazon recommends products — both hiding "irrelevant" information and only showing what they think you will like.
This type of design pattern, where user choice is removed, has recently been coined "anticipatory design". Its aim is to leverage data on user behavior to automate the decision-making process in user interfaces. The outcome lowers the excessive number of decisions people currently make, thereby reducing decision fatigue and improving decisions overall.
We might not realize it, but as developers, we build inaccessible websites all the time. It's not for the lack of care or talent though — it's a matter of doing things the wrong way. In our new book, Inclusive Design Patterns, Heydon Pickering explains how we can craft accessible interfaces without extra effort — and what front-end design patterns we can use to create inclusive experiences. Quality hardcover, 312 pages. Get the book now!
Now, accessibility has always been a slightly unsettling realm for web developers. Surrounded with myths, misunderstandings, and contradicting best practices, it used to be a domain for a small group of experts who would "add" accessibility on top of the finished product. Today, in many simple and complex websites, it's still unclear what makes up an accessible interface and what developers need to know in order to achieve it.
Whether or not you celebrate Halloween, there is something magical about that special spooky day, surrounded by mystery, horror, scare and trick-or-treat candies for kids and adults alike.
In this post, we celebrate the creative side of Halloween with those of you who are also planning to celebrate with friends. The post features artists around the world who have been creating wonderful illustrations dedicated to Halloween.
In the past few months, chat bots have become very popular, thanks to Slack, Telegram and Facebook Messenger. But the chat bot idea is not new at all.
A chat bot interface is mentioned in the famous Turing test in 1950. Then there was Eliza in 1966, a simulation of a Rogerian psychotherapist and an early example of primitive natural language processing. After that came Parry in 1972, a simulation of a person with paranoid schizophrenia (and, yes, of course, Parry met Eliza).
But then again, we have to remind ourselves that we shouldn’t immediately jump to a new tool just because it’s available, to not rewrite the whole code of a project just because conventions have changed. No project will stop working because you’re using OOCSS instead of ITCSS or Backbone.js instead of React.js. If the project is an ongoing process and will be developed and maintained for another few years, you should evaluate to change tools from time to time, of course. But take your time. Better evaluate first, then reconsider, before you immediately jump on a train from which you don’t know where it’s heading.
No thorough conversation about the front end today can end without mention of pattern libraries. Sometimes a pattern library appears in the form of a living style guide, or as a design system, or as the outcome of an atomic design process, or as an all-knowing user interface framework. In all of these cases, designers and developers seek the right strategy to approach the complexity of the web with a modular, components-based approach.
However, finding the right way to architect a lasting pattern library and to integrate it into an existing workflow seems to be a challenging task and one that most design and development teams eventually give up on. In this article, I’d love to highlight some practical techniques and strategies to establish a lasting pattern library that will be actively and consistently used by the entire team. These tips might help you get on the right track when you set out to build your next style guide, assets library or design language.
According to browser statistics, Chrome for Android is currently the largest mobile browser, or is about to become so. Still, too few web developers realize that these Chrome for Android numbers in fact contain several browsers, not just Google Chrome. After discussing the general state of affairs in this article, we’ll focus on the Chromium-based Samsung browser specifically.
In the past few years, just about all Android device vendors have upgraded their default browsers to Chromium… but not to Google Chrome. Instead, they took an older Chromium version of their choice, modified it somewhat, and added it to their devices as "Internet" or "Browser."
Web and mobile apps are moving away from pages towards completely personalized experiences. These new experiences are built on an aggregation of many individual pieces of content. The way this content is now being presented is in the form of cards. The card-based interaction model is spreading pretty widely, and you can see digital cards almost everywhere — from news sites to food delivery apps.
In this article, I'll explain what cards mean to UI designers, and I'll review three popular card-based services. If you're interested in prototyping your own card-based user interface, you can download and test Adobe's Experience Design CC for free and get started right away.