We had a meeting to discuss the technical choices to start the implementation of the guided tutorial extension (or any other name we end up with).
And while discussing, we realized that we don’t have enough information to make a choice.
See below a list of questions we were unable to answer:
- Do we still want to be able to focus on specific elements during a step?
- In Proposals for improving the Onboarding Experience - #18 by gabrielc and in the ASCII mockup we can see checkboxes. When and how do they change state?
- How do we know if an achievement condition is met?
- Since the tour is “guided”, what happens when the achievement condition is met? Taking an imaginary use case where the user is asked to type “hello world” in a field, then asked to press a submit button once “hello world” is typed
- What happens right after “hello world” is typed?
- Is the user moved to the submit button?
- Is the move done with a delay or a transition?
- Or does a checkbox become checked and the next step button enabled?
Overall, I think we need example scenarios to better understand the user flow of the guided tutorials.
Furthermore, given the extensible nature of the extension, what happens when two tutorials can be activated for a given user at the same time?
- Are they merged?
- Is one of the tutorials put on hold until the first one is done, before being proposed to the user?
I’m also wondering if we want to have a precondition for a tutorial to start, for instance:
- An introduction tutorial starting on the first login of a user.
- An admin tour the first time a user accesses the administration
- An edit tour the first time a user clicks on the editor button
- A “more actions” tour the first time the user clicks on more actions (or maybe just after a predefined duration, and only once the introduction tutorial is completed)
What happens if a user discards a tutorial? Are all the future tutorials discarded as well?
cc @tkrieck since the answers might impact your UX design.