| > "Tutorial screens and mechanisms are never a good thing." What's your definition of a "good thing" or "actually good"? If it's quantifiable as higher engagement and retention then these mechanisms are far from "never a good thing". They're a good thing quite often - when done correctly. This is why you see them in many products that have growth teams dedicated to the task. Agreed that the screenshots do not do a great implementation justice. Note that when I'm talking about onboarding, I am talking about combining introducing users to the UI with introducing them to the product. Sure introducing the user to UI by itself is not great. > "If you've designed an experience that is intuitive and requires no tutorial screens, you want to include them anyways? Am I reading your post wrong?" Slightly yeah. It should be read as: "If you've designed an experience that is intuitive and requires no tutorial screens, you want to test them anyways." Because we've seen their inclusion improve engagement and conversion even in experiences that are intuitive. Sometimes that's not the case, but the possibility is strong enough to justify testing them out. |