Cool js, but I absolutely despise websites or software that do this.
Driver.js: Product tours, highlights, contextual help and more
91–100 of 108 posts
Re: Driver.js: Product tours, highlights, contextual help and more
#92Earlier quoted context omitted.
People not knowing some of the features is not really a problem, because it doesn't matter. Every single one of my elderly relatives can use an iPhone after a quick intro and they don't need help afterwards. The device is essentially self-serve once you understand one or two core ideas. Them not knowing about some features is not a problem, they can do all the important things without someone helping them out. No oth…
> People not knowing some of the features is not really a problem, because it doesn't matter It does matter. I started using a iPhone maybe a couple of years back, after using an Android phone for many many years, and I still find out stuff randomly by chance that they could have just told me about. Biggest example when I just got the phone, took me maybe a couple of days before I understood that swiping from the top…
My non-English-speaking first-gen immigrant grandma that assembled rice cookers in factories back in her day figured slide down for notifications, right slide down for control panel, and slide up on day 4.
My mom didn’t ask about it until after the first year.
So to answer your question… maybe it doesn’t take to be the top 1% of something.
Re: Driver.js: Product tours, highlights, contextual help and more
#93If anyone is looking for a jQuery days version of something like this https://zurb.com/playground/jquery-joyride-feature-tour-plug...
Really wish Zurb would release a jQuery free version of Foundation. I prefer it to Bootstrap, its lighter weight, but would be much lighter if they stripped jQuery and made it pure JavaScript/CSS.
Re: Driver.js: Product tours, highlights, contextual help and more
#94Tours aren't always bad, but they're often just poorly implemented, with too many steps that don't mean anything to the user. Onboarding that's contextual, like embedded tips, or relevant, like targeted onboarding by persona, or action-oriented onboarding, like checklists tend to be better. After leading onboarding and in-app education teams at Dropbox, I started Dopt [0], which is a react component library and SDKs…
why does your website need to gather cookies? first thing I'm hit with is a cookies splash screen, I'm wondering what I'm being tracked for.
I'm also curious about this:
>Hybrid work
On the face of it, I like the upfront callout, however how did you guys land on Hybrid being the solution? Especially in the light of working 100% remote leads to more productive employees[0]
[0]: https://thehill.com/business/4110598-remote-employees-work-l...
Re: Driver.js: Product tours, highlights, contextual help and more
#95Earlier quoted context omitted.
The difference is it's intuitive to discover. Once you discover this does something here, you start wondering where else could this happen? You might wonder if you can adjust the iPhone flashlight brightness. For me it was intuitive to long-press the icon in control center to find more options and I was delighted to discover that's exactly how it works. Those little moments of delight and synergy are why I choose the…
Half the time it does something, I don't know what I did, and I'm in a rush and so instead of sitting down and having a happy little moment I'm annoyed at having it do some unexpected, unrepeatable thing.
I have never found that the case in iOS. Anything I click / do unexpectedly I can reliably repeat the steps 99% of the time, it's why I prefer iOS over Android with apps that can modify the OS.
Re: Driver.js: Product tours, highlights, contextual help and more
#96Tours aren't always bad, but they're often just poorly implemented, with too many steps that don't mean anything to the user. Onboarding that's contextual, like embedded tips, or relevant, like targeted onboarding by persona, or action-oriented onboarding, like checklists tend to be better. After leading onboarding and in-app education teams at Dropbox, I started Dopt [0], which is a react component library and SDKs…
why does your website need to gather cookies? first thing I'm hit with is a cookies splash screen, I'm wondering what I'm being tracked for. I'm also curious about this: >Hybrid work On the face of it, I like the upfront callout, however how did you guys land on Hybrid being the solution? Especially in the light of working 100% remote leads to more productive employees[0] [0]: https://thehill.com/business/4110598-rem…
For cookies: we're using Posthog for tracking and it's helpful for us to understand how people use our website and product.
Hybrid vs remote is sometimes polarizing, but hybrid has been really great for us to balance the heads down time and no commute of remote with being able to jam on stuff in person.
Re: Driver.js: Product tours, highlights, contextual help and more
#97Earlier quoted context omitted.
why does your website need to gather cookies? first thing I'm hit with is a cookies splash screen, I'm wondering what I'm being tracked for. I'm also curious about this: >Hybrid work On the face of it, I like the upfront callout, however how did you guys land on Hybrid being the solution? Especially in the light of working 100% remote leads to more productive employees[0] [0]: https://thehill.com/business/4110598-rem…
For cookies: we're using Posthog for tracking and it's helpful for us to understand how people use our website and product. Hybrid vs remote is sometimes polarizing, but hybrid has been really great for us to balance the heads down time and no commute of remote with being able to jam on stuff in person.
Interesting. When Hybrid was made as a decision, where there any data points that were considered in that decision, or was it just made from the start, or top down?
Do you think its not possible to have the same levels of collaboration remotely if the culture adjusts for remote only type expectations?
(I rarely get to ping decision makers about these things, I apologize for the intrusion, I'm trying to gather as much data on this as possible recently)
Re: Driver.js: Product tours, highlights, contextual help and more
#98This looks great. What does it do differently to Shepherd[0]? [0]: https://github.com/shipshapecode/shepherd
Here's some community information regarding the two https://devboard.gitsense.com/shipshapecode/shepherd https://devboard.gitsense.com/kamranahmedse/driver.js The popularity for driver.js has grown significantly in the past few weeks. Not sure what is the reason for it though. Full disclosure: This is my tool
Your tool looks great, and I was never a huge fan of shepherd. I just wanted to know the objective differences between the two, or your reasons for building it. I'd already looked at the repository stats.
Re: Driver.js: Product tours, highlights, contextual help and more
#99No no no no no. Design your product to be understandable at first pass. Apple famously doesn't do any of this with your iPhone, while Sony forces you to do it on every new device. Let the onboarding be a forcing function for usability. This isn't a crutch, it's something worse and damaging.
I guarantee 99% of iphone users dont know 50% of iphone features. You have drunk far too many apple marketing paragraphs.
Re: Driver.js: Product tours, highlights, contextual help and more
#100Earlier quoted context omitted.
For cookies: we're using Posthog for tracking and it's helpful for us to understand how people use our website and product. Hybrid vs remote is sometimes polarizing, but hybrid has been really great for us to balance the heads down time and no commute of remote with being able to jam on stuff in person.
Interesting. When Hybrid was made as a decision, where there any data points that were considered in that decision, or was it just made from the start, or top down? Do you think its not possible to have the same levels of collaboration remotely if the culture adjusts for remote only type expectations? (I rarely get to ping decision makers about these things, I apologize for the intrusion, I'm trying to gather as much…
All 3 founders worked remotely at larger companies during the pandemic and when we started the company in late '21 we knew we wanted to be hybrid, so it was made top down from the start. For a small team, I personally think there are culture and productivity benefits for being in person. I think other companies have shown remote is absolutely viable for small and large companies, but to your point, there has to be a lot of intention around it. I don't buy into the dogmatic views of hybrid vs remote: I think it's more about understanding what's right for you and the company, and as a leader making the culture, policy, and practices work for what you want. For me and Dopt, hybrid has been a dream :)