Skip to main content

I was genuinely excited about this new feature, not just because it helps reduce the double dipping on seat pricing, but because it seemed like a much simpler way to collaborate with external teams and clients who have their own Figma accounts.

Unfortunately, the current limitations around the very minimal number of connections make it feel fairly useless, especially for a small agency like ours that work with multiple different teams every day. I had hoped this would be similar to Slack’s connection feature.

More importantly, the feature still feels underdeveloped. Our team typically sets up two folders per client: 1 internal for exploration and iteration, and 1 external for sharing polished work. We were hoping the connected projects feature could replace our external folder and streamline collaboration. But when we tested it by adding a completed website and design system to a connected project for the client’s team to use, we quickly ran into an issue. Our team couldn’t access the design system library we had built in our internal project because we weren’t the host of the connected project. And if we became the host, the client would face the same problem on their end.

I love Figma and use it literally every day. I genuinely want to see it keep improving, and I think addressing these 2 issues would make team that collaborate around the world a LOT happier.

Be the first to reply!

Reply