Skip to main content
Notamisanthrope
January 29, 2021

Repeater 🔥 (Auto-Layout evolution)

  • January 29, 2021
  • 42 replies
  • 13364 views

Hey guys,

Let’s be real. The main spectrum of work with UI, whether it’s an app, or a website, is displaying data or content (such as feed, lists, posts, comments, etc).

We can do a component of a post card, for example. Then duplicate instances, and wrap that in an auto layout.

It would be cool to have a repeater that shows right up after you’ve activated the auto-layout, where you can specify how many times to repeat the instance (component) and bind data to it.

At the same time, it would be cool to have a centralized data location somewhere (i.e. when you click on the data, open a shared data set so that the same data can be accessed from different repeaters).

(Screenshot is just to deliver the idea, it’s far from the perfect UI, I didn’t spent much time of thinking it through since Figma has a great product team on board to elaborate it and deliver in an amazing simplified way)

It feels like it’s a very natural evolution of Auto-Layout feature.

So, what do you guys think?

(P.S. Sorry for my English, it’s my second language)

42 replies

AlicePackard
Power Member
February 10, 2022

@ashygee, this is a really interesting concept, and thank you for making a video demo to go with it! Having a feature like this would jive so well with the way I work. I tend to make everything a component as a workaround for a lack of native content/data management, and I can see how this “dynamic child” concept could help greatly:

To use your Menu and MenuItem example for how I achieve the same results today: I would set it up exactly as you did, but when it came time to mockup a screen or prototype with real(istic) content, I’d to create a component that contains all the MenuItem instances I need in an auto-layout frame with overrides applied to the text, might name it “MenuItems / Content Overrides.” Then, in an instance of “Menu” I would swap the single nested “MenuItem” inside it for “MenuItems / Content Overrides”

So for files used to make mockups and prototypes, a feature like what you’ve suggested could drastically reduce the total number of components I’d need to make which would be great for file organization, and likely performance as well.

I write about building excellent Figma components on my blog: https://alicepackarddesign.com/blog
Richard_Doyle
June 8, 2022

Saw a new component properties video today that had like 10 toggles - show row 1, row 2, row 3, etc. Shows how silly things get when you can’t define a repeating portion of a component. Please consider this soon!

Jenni_Merrifield
New Member
July 21, 2022

I was just doing a search today to see if the application had anything like this. We recently moved from Axure to Figma and it’s one of the components that Axure provided that I am definitely going to be missing.

Ish
New Member
September 1, 2022

Would love to see this, with the recent property changes I’d hope this is another step closer to being a possibility. As described this would pretty much mirror the Repeater function in Axure, which I’d love to se in Figma.

Data heavy pages with tables or cards would be a breeze to mock up with this.

Darko_Antanasijevic
September 17, 2022

@Figma_Team - please support repeater (like Invision Craft Data plugin for Sketch), XD Repeat Grid, or similar functionality. Please note that having pre-defined data as in Craft plugin is convenient, but having custom data source is essential for corporate/enterprise UX design. Data source can be a plain text file as in XD, Google Sheets data table or something else, as long as there is a way to map a specific column to the specific content container in your data template.

ca-sey
New Member
November 8, 2022

How could this not exist yet???

Nick_Mosher
December 6, 2022

This would be amazing. Please consider it.

Ilakkiaselvan_Subbiah
New Member
January 6, 2023

Coming from sketch and Xd I feel missing this feature badly, I spend more time in tables duplicating rows than seeding on important stuff.

Keegan_Foster
New Member
January 31, 2023

Bumping this - what a pain it is to create for example a table component in figma currently - impossible to duplicate rows and columns without detatching the component and losing all interactions.

Dan_Flynn
New Participant
February 6, 2023

Agree, been waiting for this for years now and would immensely benefit from having a repeater field built into Figma.
Maybe they’re waiting to add this along with a native CMS? 🤞

Please add this Figma! Bump : )