An interesting model for collaboration in Figma, borrowing the best practices from the software development world. It defines a process where the team is solving one problem at a time by structuring the project in a specific way, applying naming conventions, and using version control.
Spelling and grammar checker for Figma. Free for files with fewer than 100 text layers.
Fantastic plugin for finding all instances of the component. I used it while migrating and unifying a large design system and it was irreplaceable.
Quick video showing real-life usage of Auto Layout in a few beautiful mockups.
Coming in the next release. So happy to see resizing moved to the top level!
We are changing it. This is what the text property panel will look like in the next release :–) pic.twitter.com/H0XhAU39gB
— Rasmus Andersson (@rsms) January 15, 2020
A common approach seems to be using a separate private project for experimenting and then moving finished work to a public place. Figma designers use this approach internally as well.
In all seriousness there is a place for collaboration and there is a place for heads down work. I hope Figma can support this.
— Tuhin Kumar (@tuhin) January 17, 2020
At minimum hiding cursors would be a start (does that exist already?).
cc @nlevin @rsms
Good to know, I faced this issue a few times before and chose to outline strokes, but this is not always possible or ideal.
Figure this Figma exporting issue out! It doesn't export properly when you have mixed caps and joins.
— Steve Schoger (@steveschoger) January 14, 2020
cc/ @figmadesign https://t.co/gQWsaluzzX pic.twitter.com/zP3pE770HD
Deep dive into Figma’s incredibly powerful and unique inventions like the Arc tool and Vector Networks.
A fascinating look at how Figma can evolve from a design tool to a visual communication and collaboration platform. Tom Johnson writes about use cases that are not possible today, but it’s exciting to think they might become a reality one day.
Use Figma for presentations? This is how to make any clicker work with it.
5 practical lessons for content designers on working content-first, collaborating with product designers, and using Figma to its wordiest potential.
A detailed guide on turning Figma design prototype into a native iOS or Android app without writing code. I’ve never used Bravo Studio before but it’s an interesting development in line with the current #NoCode trend.
Figma’s Director of Product wrote a detailed explanation of why layers are ordered backward inside an Auto Layout frame. This thread is a good illustration of how many factors have to be considered even for a seemingly simple design choice.
A lot of people have been asking why the items in an Auto Layout frame go backwards in @figmadesign.
— Sho Kuwamoto (@skuwamoto) December 10, 2019
I usually hesitate to answer seemingly simple questions that end up requiring super long answers, but... here we go!
1/n
An interesting observation that what we need next is states, styles groups, and variables. Yes, please!
Auto Layout can be used for so much more than just buttons and lists. This post shows how useful it is for working with copy and images.
Not sure if this post should be called “quick tips” as it mostly surfaces unresolved problems, but it’s an interesting look at the limitations of the current implementation.
An in-depth tutorial covering 3 common use cases for Auto Layout — button with an icon, content card, and a chat log screen.
A boilerplate for developing Figma plugins that take care of setting up and configuring TypeScript, Webpack, ESLint, Stylelint, Prettier, Jest, EditorConfig, etc.
After Smooth Shadow generator made rounds in the design community, its author built a matching Figma plugin. It’s the easiest way to build a nice smooth shadow, and as it’s based on a box-shadow CSS property it’s easy to export and reuse in code later.