What is Figma?
What is Fluid UI?
Need advice about which tool to choose?Ask the StackShare community!
Why do developers choose Fluid UI?
Sign up to add, upvote and see more prosMake informed product decisions
What are the cons of using Fluid UI?
What companies use Fluid UI?
Sign up to get full access to all the companiesMake informed product decisions
Sign up to get full access to all the tool integrationsMake informed product decisions
The tool we use for editing UI is React Storybook. It is the perfect place to make sure your work aligns with designs to the pixel across breakpoints. You get fast hot module reloading and a couple checkboxes to enable/disable browser features like Flexbox.
The only tricks I apply to Storybook are loading the stories with the mock data we’ve extracted from the API. If your mock data really covers all the various various possible states for your UI, you are good to go. Beyond that, if you have alternative states you want to account for, perhaps loading or error states, you can add them in manually.
This is the crux of the matter for Storybook. This file is entirely generated from Yeoman (discussed below), and it delivers the examples from the Alps Journey by default. getSectionsFromJourney() just filters the sections.
One other hack you’ll notice is that I added a pair of divs to bookend my component vertically, since Storybook renders with whitespace around the component. That is fine for buttons or UI with borders, but it’s hard to tell precisely where your component starts and ends, so I hacked them in there.
Since we are talking about how all these fabulous tools work so well together to help you be productive, can I just say what a delight it is to work on UI with Zeplin or Figma side by side with Storybook. Digging into UI in this abstract way takes all the chaos of this madcap world away one breakpoint at a time, and in that quiet realm, you are good down to the pixel every time.
To supply Storybook and our unit tests with realistic mock data, we want to extract the mock data directly from our Shared Development Environment. As with codegen, even a small change in a query fragment should also trigger many small changes in mock data. And here, similarly, the hard part is tackled entirely by Apollo CLI, and you can stitch it together with your own code in no time.
Coming back to Zeplin and Figma briefly, they're both built to allow engineers to extract content directly to facilitate product development.
Extracting the copy for an entire paragraph is as simple as selecting the content in Zeplin and clicking the “copy” icon in the Content section of the sidebar. In the case of Zeplin, images can be extracted by selecting and clicking the “download” icon in the Assets section of the sidebar.ReactDesignStack #StorybookStack #StorybookDesignStack
If it weren't for legacy projects that are still haunting us, Figma would pretty much replace a whole fistful of tools we used to need.
We use it in our newser projects and freaking love it.
- Endless Design-File versioning.
- OS independent (Runs in the browser)
- super fast and performant
- Smart handling of components and styles
- easy sharing
- multiplayer editing of files. :D
- so many other smart features.
- Prototyping (pretty basic but much more to come as well)
Highly recommended. You should really give it a try.