Hacker Newsnew | past | comments | ask | show | jobs | submitlogin
Show HN: I created a library to create product tours / walkthroughs (lusift.vercel.app)
62 points by nbhusal on Aug 18, 2022 | hide | past | favorite | 12 comments
This is significantly different in its feature set than the existing open source alternatives, I made this to be a more complete library, and well, as a portfolio artefact. Any comment is greatly appreciated. Thank you!

Code: https://github.com/lusift/lusift




Documentation locked up in walkthroughs is very frustrating to access. You can't search for it or reference it easily.

Mini-tutorials upon open are so annoying that my brain immediately enters "get out of the tutorial at any cost" fight-or-flight mode and I start scrambling for a hide, skip, or close button. If I don't find one I close the app and give it a 1-star rating that it has unskippable tutorials.

As far as I can tell, this is a really well executed version of something that drives at least some subset of users (and possibly more) totally nuts.


You are likely not the target audience. This cohort of "some subset of users" that prefer things to be textually rather than visually based is quite small outside of software developers.


I'd love to see some user testing data on the subject. I feel like investing in tooling around the tutorials would be predicated on evidence that more than 50% of users benefit from them.


Here's the thing: if done right it can have a _massive_ impact. One onboarding experiment I ran in a past life doubled trial activation.

Trouble is that lot's of people do onboarding poorly. What you and the parent comment call out is a failure mode: to build effective onboarding you need to understand who you're building it for and what they're trying to accomplish. A tooltip tour approach might be effective for certain kinds of products/users/use cases, and extremely ineffective for others.

What I've seen be most effective (at least for B2B SaaS products):

1) tailoring the experience so people are being onboarded in ways that are relevant (e.g. their role, are they the first user or nth user, their use case/job to be done, how familiar they are with the domain/similar products, etc...) and

2) do>show>tell: get people to use the product to learn how it works vs plastering signs all over it. Which modalities are most effective is product/user/context dependent.

Source: I've been responsible for onboarding at a few SaaS companies now (and am now building a platform in the space)


But would it hurt anyone to have them only optionally launched? A little clippy-like thing saying Hey there's a walkthrough here if you want it; not in your face if you don't.


Requires a bit more code, but I do find this compromise attractive. Let's try to make this the default.


Looks great! Can I use this for my product's onboarding instead of https://www.appcues.com/ ?


It was intended to be an open-source alternative to appcues and the likes, yes.

Let me know how it goes =)


This is great. We have tried userpilot for our SaaS product but this seems like a great open source alternative ! Good Job


Opened the documentation link, clicked on the ‘Open Demo App’ and decided to return to the documentation link page. The back button on my browser doesn’t work. I’m stuck on the demo app page even though I haven’t activated/entered the App. It could be this is caused by my iPad itself. If not, it’s not good when a site ‘hijacks’ your browser back button and prevents you from leaving a page.


Looks great, we are using angular, but would like to give a try


Firefox seems to be not supported...




Consider applying for YC's Fall 2025 batch! Applications are open till Aug 4

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: