Getting On Board?
Getting On Board?
Okay you wrote an app and people are actually using it—amazing! But how do you ensure that they keep using your app? Here are some pointers about how to keep your user base engaged.
Join the DZone community and get the full member experience.Join For Free
So how bad is the retention on mobile apps these days? Pretty bad, you probably guessed; but this bad?
According to studies, one in four mobile apps is abandoned after a single use. So apart from focusing on first impressions and engaging users during the first launch you should think about how to keep bringing them back over time… Ask this question before you start building anything: How can I ensure that users will keep coming back?
- Start a drip email campaign during onboarding.
- Update users with their results by email.
- Use personalized notifications: push, SMS, chat bots.
- Leverage of social mechanics.
Read the whole thing — the infographics are great. For more perspective on long-term retention, check out
Yes, the initial goal of user onboarding is to teach someone how to use your app. But if all a user has done is learned the ropes of one feature, the job isn’t done. Good user retention means going far beyond basic user onboarding. Retention has many stages, and if you want to keep your retention numbers high, you need to think about user onboarding past the first day…
For some specific tips, check out:
It’s easy to make onboarding exclusively about the product—logistics, how-tos, and the nitty-gritty details about your product. But your onboarding still needs to be all about the customer. That starts by creating a seamless user experience centered around buyer personas and jobs-to-be-done to align the promise of your product with the onboarding experience…
A common theme you’ll notice here is exposing only appropriate functionality. Why, a “design pattern”, we could call that idea:
Progressive disclosure is a strategy for managing information complexity. When you use progressive disclosure, you show only the information necessary at that point in the interaction. And you display more advanced functionalities of the app interface as the user interacts with it…
A most important aspect of that progressive disclosure is to never ask the user for a permission when there’s any chance they might refuse it, as they probably will if the benefit is not obvious and immediate. Good advice here:
When it comes to requesting permission, the worst thing an app can do is to bombard users with permission requests without any notice or explanation. Both asking your users for permission too early or for too many things at once are common mistakes. And yet, many apps still do that…
So there’s plenty of food for thought. Some more links with gritty details you may find useful:
Onboard is a particularly clean and simple framework for quickly adding onboard screens.
Published at DZone with permission of Alex Curylo , DZone MVB. See the original article here.
Opinions expressed by DZone contributors are their own.