The material design guidelines has this great component :
https://material.io/guidelines/growth-communications/feature-discovery.html#feature-discovery-design-patterns

@jadus Have you come across this in the wild, either on Google's or other apps? I'm not saying it hasn't been done, but this doesn't seem from my experience to be a pattern that has made it outside the designers' sketchbook.
In fact other than that screenshot, I'm not seeing anything that indicates how it should behave: animation, interaction model, etc.
If you would like to put something together for the lab (as @oliviertassinari suggested), to explore the possibilities, you're welcome, but I don't think it will get much traction otherwise.
but I don't think it will get much traction otherwise.
@mbrookes I agree. I have added the lab flag to be kind. But I believe the "most probable" path forward is a third party library that implements it.
Well yes I've seen it on google apps (inbox, keep, calendar)
I think it's very useful when you have new features coming in an app or when you want to introduce features at the right time.
Btw I want to thank you for this great library, my app looks great thanks to it : https://www.sboulder.com/
In fact it's named "feature discovery" and there's all animation and everything described in the guidelines. I edited the issue title and description.
Would love to see this feature.
This would be a really nice addition or third party component. But it looks like that link to the spec is no longer working. Maybe it's been removed?
Here you go (Material-UI based): https://github.com/TeamWertarbyte/material-ui-feature-discovery-prompt
Wow how did I miss your project ?
Thanks
Not mine, @leMaik's. 馃憤
New specs are somewhat described here https://material.io/design/communication/onboarding.html#quickstart-model
芦Prioritize the first key action禄

I have added the waiting for users upvotes tag. I'm closing the issue as we are not sure people are looking for such abstraction. So please upvote this issue if you are. We will prioritize our effort based on the number of upvotes.
I do agree an onboarding component would be used by many / any applications built atop MUI. Would see consistent use. I'd use it right now, for example
i can add share my source code for this if you'd like...i rebuilt it to use modern hooks, etc