Intro.js aim to deliver better introductions for websites and features with a step-by-step guide for your projects. I got the inspiration for a little pull request after having read a great post by Jan König titled “Batman Onboarding”.
In that article, Jan writes about what’s wrong with onboarding wizards, outlining four main issues:
- Introducing all the features
- Not based on user behavior
- Too much friction
- People want to be in control
His third point, “Too much friction”, where he state how often onboarding wizards are not a part of the core user experience, but merely a layer on top of the product, made me think about those cases and how we could help them. It’s clear to me that top class teams and products, like the slack example he shows, know how to deal with those issues. But, what about all the smaller projects, apps and sites out there that don’t have all the resources or know-how needed to provide better onboarding experiences, and instead rely on off the shelf solutions like intro.js? Can something, that may not feel right, could partially address the other issues mentioned by Jan? Let see…
I’ll skip the “Introducing all the features” issue as with intro.js you have the power to decide what features to include in the intro from within your code. So, I’ll focus on the “Not based on user behavior” and “People want to be in control” issues, that are pretty tight together anyhow:
The user has only one chance to be guided through the onboading flow: right after signup. So people who just want to play around and discover some features close the wizard immediately and don’t know how to get back when they really need to be guided through the product.
Having no choice in the first steps they’re taking is obviously not a satisfying first-run experience.
What if, through intro.js, an user could both retrieve the wizard and decide where to start from in that wizard? That’s exactly what my pull request for intro.js try to solve.
How it works
Batman will transform the intro.js steps defined in your markup into helpers (bringing them to the user in a “Pow / Ka-boom” style animation), that once clicked, will start the wizard from that specific point. Check out the demo to see it in action.
How to use it
We just need to call intro.js via its new batman API. This could be done via a click event: (Batman works as a toggle)
Under the hood
First an array containing the intro.js steps found on the page get created, together with an array of batman helpers (In case batman has been already fired).
When invoked, the batman method will either add helpers on the page or remove them (in the case it has been already fired), following a toggle pattern.
Is important to know that for batman to work you must use the intro.js data-step attribute when defining the steps in the html.
By looping trough the steps array, batman will create for each item an html element (the helper) in the form of a span, appending it to the DOM. Every helper will contain an onclick attribute to fire intro.js. Similarly, if any helpers is found on the DOM, the method will remove it following the toggle pattern.
Is important to know that the batman method can accept any options that you will normally pass as argument to intro.js itself. It will use those arguments when firing intro.js later from within an helper, like:
Animations are handled purely via css.
Final words and links
Take this as a proof of concept showing how some onboarding issues, as the ones outlined by Jan König in his post, could be addressed on a generic, off the shelf solution, like the popular intro.js.
If you have any question, comment or feedback, please get in touch on twitter or drop me a line at nick at balestra dot ch.