Are you throwing up roadblocks to your users before they’ve Activated in your App?
When a user is getting started – quite often there won’t be any data for them to visualize how your product can help. This is a called an Empty State.
What is a UX Anti-pattern? What are common examples or poor and good Onboarding experiences?
Empty States in Onboarding
Smoothing the path for your users and assisting them in their experience can not only help in preventing damage and loss, but enables you to prove your product’s potentials.
What we suggest here is a series of methods to fill up the gaps in the user’s experience, get them invested in your product, delay the pinpoints or moments of doubt and try to get them to the “aha” moment as easy as you can.
Address Empty states:
These might be translated as you leaving your users alone and confused. Instead, it’s very important to use these states as opportunities to show them the true value that you provide.
Here are some suggestions:
- Use mock data to fill up charts or diagrams
- Show useful starter content. For example, when the user registered did they provide any information about their role/user-type, key use-cases? You can use these to build some initial records that speak to their stated needs.
- Assist with tips, announcements, or videos – use a tool like Contextual to run Guides and see if this increases activation.
Believe it or not, users trade their information in exchange for your service. Getting users invested in your product is the key to get you the information/data you require from them. Delay the moments of doubt or whatever that might be translated as pinpoints and let them explore your services as much as possible.
Keep the experience consistent:
If you provide services for more than one platform, creating a consistent and smooth experience for your users can help their overall impression of your services.
In the video below is a presentation (snippet) from Bess and David where they cover some actual patterns and anti-patterns in Mobile App examples to compare with.
In a followup post we will cover one popular B2B webapp (Monday.com) and summarize some patterns and antipatterns we’ve come across – especially for Mobile Apps!