Ok. I linked all the components from Figma to Storybooks. (It's not mapping out perfectly because we don't live in a perfect world, there are countless example where this is not working). Now the QA and dev team is aligned. Then what? That's it? That's just a workflow enhancements? What am I missing?
Great talk! Helped and greatly inspired both me as a developer as my fellow design colleagues! Great work!
Ok. I linked all the components from Figma to Storybooks. (It's not mapping out perfectly because we don't live in a perfect world, there are countless example where this is not working). Now the QA and dev team is aligned. Then what? That's it? That's just a workflow enhancements? What am I missing?
Yeah pretty much, it's another way to catch the "this is wrong" before it gets to the production server.
@@TravisHi_YT good answer
great video but as unfortunate that would be more great if your focus more on the tech side than making accent
Nice presentation, very distracting use of "folks" though, and I wish you emphasised that Chromatic is a paid service, whereas storybook is not.
Couldn't get the plugin to work, but what's new with Figma 🤣
They may need to check their storybook for any issues with storybook! ;)
What about showing the real use case of this product? I tried chromatic, its useless for me as a designer, and its useless for developers as well.
This doesnt improve adoption at all
Reeeee