In 2016, Sticky Password approached Proof & Reason–where I was working as a UX designer at the time—with the redesign project of their current app ecosystem and I was to lead the design efforts.
The project turned out to be long-term cooperation: I was embedded in the product team and we worked closely on the redesign itself, but also on a couple of new addition and improvements.
Sticky Password + Proof & Reason
Sticky Password was planning to rewrite their apps using newer technologies. The UI was somewhat dated at that point and there were inconsistencies across platforms.
This presented an opportunity to:
Early on, we established the principle of "evolution, not revolution". We wanted to give users a better experience, but not at the expense of taking away what they were used to. This wasn't a time and place for a radical redesign.
The initial state of the app's UI
It was necessary to quickly get to know the product. To do that—and to better empathize with users—I became a user of Sticky Password myself. This allowed me to see opportunities for improvement and to keep the "evolution, not revolution" principle in check.
This couldn't substitute research though. Fortunately, I was able to work with personas from previous research as well as usage data of the current app.
Focus was on the desktop apps' design first, because they were used the most heavily. I kept the main layout unchanged (left menu and content on the right), but iterated on the content layout based on usage data and to accommodate for upcoming features.
Good scannability was a priority and because Sticky Password has a wide range of user groups, I was quite conservative with the UI design to ensure universal usability.
It was also important to make sure the design would work in many different languages that Sticky Password is available in.
Running Sticky Password for the very first time requires taking several steps including creating an account. We needed to make this process as smooth as possible and guide users through the process. For the best experience, we wanted them to enable cloud sync and install a browser extension.
Sharing passwords was an important new feature from the business perspective as it was primarily targeted for companies rather than for personal use. It would allow users to share passwords with either full or limited rights depending if they wanted to allow others to edit shared items.
We wanted to give users a better overview of how secure their passwords were. We designed a security dashboard that would inform users about passwords security. Most people don't create very strong passwords and they also reuse them very often, which is not a good security practice. The dashboard was designer to bring awareness to this and allow users to fix it – ideally by generating a strong password in the app.
After desktop, it was time to bring the new design to Android and iOS apps. The biggest challenge here was to balance the style from desktop with the guidelines of both platforms. I was mindful not to violate mental models that users could have from using existing apps or even when coming from desktop.
At the end of the day, browser is where the password manager is used most often, but the extension supported only necessary features like filling in passwords. With the redesign, we wanted to bring more functionality from the desktop app into the extension to make the whole experience more seamless and faster.
This was my first time working on a product of such scale. It taught me a lot about product development and about designing for a cross-platform experience. It was a great opportunity to learn about designing desktop apps as well.
About a year and a half after the project started, I changed jobs. This meant I wasn't able to continue working on this to see it through production and release, but it was great to see that the redesign started to be rolled out recently and I'm proud of the team that has worked on it.
(c) 2020 Adam Amran