This is the process we will look at:
The series of screenshots is here:
Screen 1: A choice
This screen offers users a choice to Sign or Register.
Plan:
Remove this screen, it has too limited (or negative) value.
We do not want registered users to have to go through this screen every time they want to log in.
The two links ‘Signup (Register)' or ‘Sign in’ can easily be added to any place where they are relevant.
Common usage patterns are the above, split links eg on main navigation, in context etc.
Screen 2: User identification
Visual / identity / background
Squint your eyes, you will see two things popping out on this screen:
a blue box
a thick red bottom
Neither of these are of prime importance to the goal here which is frictionless identification by the end user.
Additionally (and this can be subjective) the style is rather dated, not contemporary.
Suggestion:
Replace the background with:
a subtle, light visual which does not scream at the user
contemporary styling (we are leading edge so the styling reflects that ?)
Lacking the updated brand guide as it will be forthcoming from Teak, Red is combined with Blue.
Gradients = today
Toned down colors = appropriate for UI.
“Footer”
The “footer” is not needed here. The less CTAs we have on this focused page, the better. It is like a landing page in this aspect.
At this registration stage, it is not the time to send users of to look at documentation. They have clicked on a ‘register’ button, let’s keep them in that state of mind.
The “Update” request
We should find a way to not have to show this message all together, throughout the system.
But, for registration it makes not much sense. By far and large, these are new users and first thing we ask them is to manually update …
