Posts, a community app by Read.cv

Thread
Jamie Sigadel
Replying to @sergiohavenson

I think I've only used it in the past when contributing to someone else's file..

Sergio
Replying to @jsiggy

Can you share the experience? Was it around designing a new feature or something small as component changes ?

Jamie Sigadel
Replying to @sergiohavenson

Unfortunately can't remember much but it wasn't design systems related, more feature-related.. And I used branching specifically as to not encroach on another designer's file setup

Sergio
Replying to @jsiggy

Thanks Jamie. Would you recommend my team to use branching ?

Jamie Sigadel
Replying to @sergiohavenson

It's not really necessary

Sergio
Replying to @jsiggy

Gotcha thanks !

Kenneth Mark Dsouza
Replying to @sergiohavenson

We’ve tried to use it and failed.

Sergio
Replying to @kend

Hey Kenneth, interesting, tell us why briefly?

Kenneth Mark Dsouza
Replying to @sergiohavenson

1. Branching isn’t a first class citizen in the Figma ecosystem. It’s hard to find branches using file search. 2. If you use a robust file structure, it’s easier to iterate with pages. 3. Navigating to the right branch was confusing for our developers.

Brent Neave
Replying to @sergiohavenson

Yeah a little. Good for quick experiments, especially with shared libraries when you don’t want unpublished changes hanging around (or worse, inadvertently published).

Ragnar Freyr
Replying to @sergiohavenson

My recommendation is that you stay away from it. If you go to far into the branch with a complex design system it becomes impossible to merge it. Even on a brand new and specced out Macbook Pro it runs out of memory too easily.