#CaseStudy — A Design Alternative for Email Verification
One of the steps that a user usually needs to do on a registration process is email verification. Some, if not most, products will ask the user to do the verification before they are allowed to log-in to the system. At this point user usually needs to open their email and click a link from that email and then, they are verified.
One of the drawbacks of this approach is the extra step that the user needs to perform before they finally be able to try the product. They are required to move from their current task within the product into another task which is checking their email.
User needs to open his email, looking for that verification email and then clicking the link from that email. But the problem is the email may or may not reach the user at that point, or even sometimes, ended up in the spam box. This could potentially reduce the number of users who ended up try the product / dashboard.
To tackle this issue, some products is using an alternative verification method which allows user to try the product / dashboard first and then the verification can come later.
The Case Study
In this case study, we took an example of a product where user can upload and sell their photos online.
A. A Very Simple Registration Form
We tried to make registration form as simple as possible where user only needs to fill-in three input boxes. Making it very simple can possibly increase the sign-up rate on this process.
B. Logging in to Dashboard Without Verification
After the user clicks on “Register Now” button, the system logs them in automatically. We don’t need any verification at this stage so that the user can perform some actions directly. In this case, they can upload their first photo.
C. Uploading Photos
After the user clicks on “Post My First Item” button in dashboard, user will be redirected to the uploading screens. They will need to perform a few tasks. In this screen, we split the layout into two: steps in the left, and actions in the right.
D. Asking Verification in Friendly Manner
At this stage, we feel like we’d need the user to be verified before finally be able to upload their photo. We then ask them to perform a verification process (either by email link or email code). A little tips here is to use a relevant illustration and also a friendly wording.
E. Photo Uploaded
After the email is verified, the system can then completing the upload process.
Pros & Cons
Verification Upfront
Pros
- Depending on the product, this approach is good if a verification is really needed before the user logged in
Cons
- We assume that the number of users accessing the dashboard will be lower because of the extra step they need to perform upfront
- User needs to do extra steps before trying out the product
Verification after Logging In
Pros
- The registration process would feel easier and more straightforward
- Good for products that wants the user to try the dashboard/product right away (this is also achievable by logging in with social media button)
Cons
- We assume that the user will feel uncomfortable that they need to verify while they are in the process of uploading photos
Interested to work with us?
Shoot your business inquiry to hello@paperpillar.com
