During UX/UI Development I have run into the problem of my onboarding process. I have an application in which it requires an account setup requiring a few preferences along with a few questions to be collected for the application to fully work properly. Should I force this onboarding process directly after account creation, should I let the user decide when to do it, and just have certain features blocked, or how else should I present this onboarding process?
1
- This is very specific for your own situation. Much more context is needed for an adequate answer.jazZRo– jazZRo2025-02-25 17:11:03 +00:00Commented Feb 25 at 17:11
Add a comment |
2 Answers
Welcome to the site! I agree with jazZRo about more context, but I wanted to add a very general remark.
Should I force this onboarding process directly after account creation, should I let the user decide when to do it, and just have certain features blocked, or how else should I present this onboarding process?
In my experience, designs work best when they convey the value of what you are doing. If your settings and features match somehow (and that is where JazZRo's question comes in), you can block a feature which requires a selection by the user, but when the user wants to use this feature, explain why the feature depends on the selection, offer the selection, and continue with the feature after the user selected what your system needs.
In this way, the user not only determines the time when to think about the selection, she also knows which feature the selection unlocks, i.e., what value the selection brings. Esp. when asking about personal information, I think it is helpful to explain the tradeoff (my personal information in exchange for a functionality - does the user agree to this "payment"?).
When designing onboarding experiences, I usually think of two utilities: balancing user freedom and the functional needs of your app, at least according to HIG and MD documentation. And with that, the key things I would look for would be progressive onboarding, user anatomy, and minimizing friction across the process. For this case, if onboarding process is essential for core functionality, you may need a soft block for this; it should guide user through before unlocking key feature and you can do this by allowing user to explore some part of the app with default setting with a touch of freedom (Allowing them to skip some screens)
