"In 2012 I outlined why we should let people see their password when logging in to an application -especially on mobile devices. Now two years later with many large scale implementations released, here’s a compendium of why and how to show passwords and what’s coming next."
"My definition of onboarding might be a little bit different than a conventional one. I define it as any time there’s an opportunity to increase the likelihood that users are successful when trying to adopt your product. It’s not just an intro tour or design patterns along those lines, but basically any time that you can close a gap between somebody who’s seeing what they can be capable of with your product and actually being successful with it."
"A world soaked in the information generated and gathered by spimes forces end-users (those of us making their way through the feature-rich vat of today’s objects) to become wranglers (those who chart paths through changing fields of object data and relationships). Complex objects bring with them personal costs: cognitive load (the personal brainpower required to think about things, talk about things, pay attention to things, be entertained by things, etc.) and opportunity cost (to make room for an additional object in your life, you have to sacrifice something you are already doing)."
"The fundamental basis of this premise is: does it solve a problem? Anyone who has had a great idea can struggle with ensuring its relevancy through a real-world problem. In this baseline, better is usually not enough. Your product needs to address the root of the problem head-on. No Band-Aids."