View the original post
Building a UI component library makes it so much easier for your team to create designs that work well, conform to your brand’s style guide, and pass their work on to the developers who ultimately code products and release them to the world.
In the long run, a UI component library saves more time and energy than you can calculate. That’s easy to forget when you’re in the middle of creating a UI component library. Depending on the size of your organization and the types of products it makes, the project could last weeks or months.
Given the difficulty of building a unique library full of reusable components, it makes sense to find an enjoyable tool for building and testing ideas.
At this point, you’re probably thinking something like, “Here comes that call to action to start using UXPin.” Obviously, Merge is a fabulous way to make code-based components. That isn’t the topic of this article, though. Let’s talk about Storybook.
Also, let’s talk about how Storybook and UXPin now integrate so your product team can finally start exploring ideas in the best code-based, atomic environment. Yes, you were correct about expecting a gentle nudge toward UXPin. You were just a few sentences early.
In all seriousness, though, let’s take a closer look at why this integration matters.
(Ideally, you already know what component libraries are and why you should use them. If you don’t, catch up by reading this article. You will learn a lot within a few minutes.)
Test radical ideas in isolated sandboxes
When you create components, you undoubtedly go through several versions before you decide which one to use. Even if you’re just making the shape of a button, the designer in you insists that you try it with blocky edges, rounded edges, slightly more rounded edges, and ridiculously rounded edges. You cannot move on to the next task until you have seen what your component looks like on the screen,
Storybook understands this, so it lets you test all of your ideas—no matter how wild they might seem—in isolated sandboxes.
You’ll discover how much time this ultimately saves you when you start working with interactive components. What happens when you click the button with ridiculously rounded edges to submit text to a website? Turns out, the edges are way too round and the button is nearly impossible for someone with accessibility challenges to use. Now, throw that one out and test the others until you find the one that works best. You can play as much as you want without influencing anything outside of the sandbox.
Related tip: Storybook now has an add-on that will help you test components to make sure they meet accessibility standards.
Your designers have pre-approved components, so they can build freely!
Atomic UI components break down the design into small pieces. Your new designer doesn’t have to stare at your style guide for an hour before feeling confident enough to make a password-retrieval request form.
Instead of working from scratch, they open your UI component library to find all of your approved components. If they can integrate Storybook with their design tool, it gives a whole new level of flexibility as well. From this point, the work becomes about as straightforward as possible. They:
- Choose an empty text field from the component library.
- Adjust the field’s size just to make sure it looks attractive on the page.
- Add a “submit” button from—no surprise here—the component library.
- Adjust the button’s position.
- Add some text so users know what information to provide.
That’s it. They don’t have to knock on your door, send you a Slack message, or try to reach you on Teams. The components in the UI library are already approved, so there’s no reason to seek permission.
This aspect alone is going to save your designers tons of time because they simply adjust components instead of creating them from nothing. Perhaps more importantly, you will have more time and fewer headaches because you get to concentrate on your work without getting interrupted millions of times a day (slight exaggeration, but it feels like that many on some days).
Designers hate code and coders hate design: Storybook is their peace treaty
How many visual designers do you know who have enough coding experience to work as developers? The answer is: very few.
How many sighs do you hear pour from your development team when your designers send over new visuals? The answer is pretty close to infinite.
Everyone knows why the disconnect between visual design and development teams exists. They don’t have a common language that makes them effective communicators. Of course, your developers are frustrated! The designers keep sending over ideas that will take too much time to figure out or they ask for tweaks in components that already exist!
Storybook erases this problem by giving designers and developers an interpreter that makes communication easier.
In Storybook, designers can combine and adjust components without knowing how to code. They just access the Controls function and make changes. It literally takes seconds to alter designs.
Just as importantly, Storybook will interpret the changes and update the design’s code. When it reaches your developers, they already have code that makes sense.
Yes, they should review and test UIs to make sure they function as intended. Yes, they should test the entire product in case some stray character ruins everything. For the most part, though, your developers become gatekeepers who can focus on other aspects of their jobs… like actually building behind-the-scenes functionality that will process payments, recommend products, and perform other tasks that help your company generate more revenue.
UXPin + Storybook = ❤️
Now that UXPin and Storybook integrate, you can move your UI component library from Storybook and use it directly in your product design and prototyping application.
You get the best of both worlds. And you get it really, really fast without any complications.
Storybook is an open-source tool, so go get it and reap the benefits.
Don’t miss out on the other side of the equation! Sign up for a free UXPin trial so you can experience the benefits of prototyping and testing products quickly instead of sending them over to your overworked development team. Play with an integrated Storybook library on trial – get started now.
The post What is a Storybook and why you need it in your product team appeared first on Studio by UXPin.