The best products start with great collaboration on low-fidelity wireframes. Blocks is a Figma plugin that features a library of components so you can create low-fidelity wireframes with your whole team - in minutes.
No reviews yetBe the first to leave a review for Blocks
AppSignal — Full-stack monitoring for errors, metrics, and logs
Full-stack monitoring for errors, metrics, and logs
Promoted
Hey, congrats on the launch! At first, I was a bit confused about why it used the entire width of my workspace, so I resized it. Then it clicked—it's like a spice rack above the stove, keeping everything within easy reach. I do have a few questions, though.
What sets this product apart from a published Figma library that I could customize and upgrade myself? With design systems like Primer or IBM Carbon, I can create and modify components with a lot of flexibility. I understand your product is aimed at low-fidelity wireframes, but it seems a shared Figma library offers similar functionality with added customization options.
Could you explain the specific advantages your product has over these established design systems or other wireframing libraries?
Hey @ohasten! Great question, it actually all started with a library like the ones you mentioned. We just made sure to keep only the ~20 most useful components to build our UI Kit, not a full design system. This way, there’s no need to search or browse items through multiple nested groups—everything is accessible with one click. Each component has a set of predefined variables that you can easily tweak to speed up the creation process unlike most design systems. We're not building pixel perfect designs so our needs were different.
We used this kit internally for years and it was called frame at that time. When we decided to share what we built with the rest of the world, we wondered what to do. Should we stick to a library and make it accessible somehow, or should we try to build a product on top of it? It happens we’re product builders, and we wanted to try something new. That's when we met the amazing @daniel_tch.
Also, we identified a few downsides over the years with libraries. The main one was constantly having to go back and forth between the Layers and the Assets panels. This is why we wanted to have a ribbon on top, like Balsamiq does. It really acts as a third panel in Figma that you can collapse when needed, and we liked that UX.
To be fully honest, there are also downsides with a plugin. For example, we did a great job on the drag-and-drop experience, but it’s still smoother when dragging components from a library. Still, we all switched to Blocks for months and I can tell you there's no going back :)
One last thing, the 'backend' of the plugin is a Figma library. We just have to publish the library to release updates to production. Amazing process!
Blocks
Mention ✪ Insights Center
Blocks
Connectiviteam
Blocks
folk
SaaS Pricing Explorer
Blocks
folk
folk
Blocks
Crew
Blocks