No time to explain. In this series of articles, I do a quick review of websites where we’ll discuss three flowchart aspects such as onboarding, killer features and dark patterns. Today we are going to focus on Cloudflare. Without further ado, let’s get into it.
#1 — Onboarding
What’s good?
Cloudflare has a smoothly designed onboarding tool (for specific purposes) and can be used as a template for other companies. Such tiny details as a password hint make me feel being taken care of.
What I’ve learned?
- Make complex things simpler
- The showcase tells you if you are required to add any specific characters or change the length of your password
User flow
#2 — Buying something on Cloudflare
What’s good?
Seems like there is nothing unusual in this process: ordinary checkout with no additional features that would allow you skip some steps and continue further.
What’s bad?
There are always extra perks for mobile checkout experience that I would prefer having here as well. These slightly different Apple/Google Pay flows help to save your customer’s time, which as we all know, is mostly valuable.
User flow
#3 — Stats View
What’s good?
I am really happy and it is very important for me to have all of my analytics in one place: my traffic, visitors, bandwidth, I can even share my statistics with a single helpful tweet.
What’s bad?
Instead of a dropdown menu for picking a date range I would rather type in the specific dates by hand. Or selecting them in a calendar board.
What I’ve learned?
- Design is never done
User flow
Outro
I feel good about the way Cloudflare is designed. There are always a few little details to add, but it seems like it’s an endless process. Hope this post helps you to figure out your own tips or find some fresh ideas.
