3

Today Figma crushed the organization

1 year ago from , UI Designer

From https://releases.figma.com/

Wednesday, September 5, 2018 What's New This Week

The Instance Swapping menu now shows you better separates local instances and instances from the Team Library

In fact, this update significantly ruins all the previous components organization. Now, after instance dropdown was clicked the 'Page name' comes first. So you have to get your hundreds of components separated on the different pages, which makes browsing the system is difficult.

The second - if you had your design system organized yesterday like "Category / State / Substate / Component Name" and you kept your hundreds of components at one page - now you're in trouble. Now you observe the mess and duplicate names while Instances dropdown was expanded. So prepare to spend hours and hours to rename everything.

Bravo, Figma. It's a really good improvement for the future, but you had to take care of it a few years ago when you made your first steps to the design market...

PS: Are there any chances to get updated with components auto-renamer soon? Please take care of your users, who didn't hold components so freaky paginated...

PPS: Hey, community, how many from there are using "Components" tab to place items on your artboards by dragging? Is this your case?

9 comments

  • Gavin McFarlandGavin McFarland, 1 year ago

    I see your problem. Because you feel that now in order for you to avoid having that one duplicated menu you need to now separate all of your components into separate pages and rename them to avoid the duplicate folders.

    1 point
  • Sergey DurnovSergey Durnov, 1 year ago

    Well, now it works as it should, but everything built by old rules is now subject to fixes. I just wanted to post my design system today, but luckily noticed this problem.

    1 point
  • Jessica Liu, 1 year ago

    Hiya! I'm an engineering manager here at Figma. We definitely want to continue improving this feature, so thanks for your feedback.

    One adjustment we'd like to make in the next release is to only show page submenus if you have components defined in more than one page. Do you think this would work for you?

    1 point
    • Gavin McFarlandGavin McFarland, 1 year ago

      This may fix the issue. I have a library for example where all the components are defined in one page however on a lot of my projects I probably have some components lying around so presumably I'd have to find this and consolidate them into one page otherwise I'll still get sub menus.

      Considering Figma has a different mental model for creating symbols compared to Sketch any component which is created automatically stays in the page it was created from. Perhaps there's still some thinking that needs to be done around this?

      0 points
    • R. Kamushken, 1 year ago

      For me every case will work, where I do not to have to rename thousands of components manually to make organization usable again... Thanks for coming here

      1 point
  • Daniel GoldenDaniel Golden, 1 year ago

    PPS: Hey, community, how many from there are using "Components" tab to place items on your artboards by dragging? Is this your case?

    ✋ I do.

    p.s. Do you legitimately use hundreds of components? If so, how? I'm curious about your workflow.

    0 points