Flex Repeater vs Table for Client Devices

I have a view that will be available to clients that needs to populate with a list of the devices they have on rental, along with a few bits of live information next to each device name (battery charge, output, etc) and some navigation buttons to get into more detailed pages of each device.

Originally I had started to design this view with a table, and it seems to be working well. But I was revisiting the flex repeater, and was wondering if maybe this would be a better option. I haven't really used either component before, so I'm not sure as to what might be some pros and cons of both. Any direction from others as to what might be the best option for this circumstance would be appreciated.

In my personal experience, I prefer a table when I need a more organized look and feel. It keeps everything nice and aligned without having to put too much effort into it, while still allowing for a bit extra with the option to render some columns as a view.

I tend to prefer a flex repeater when I need a list of items with a bit more of a custom look and feel to something, it takes a good bit more effort usually (for me). For example, the table automatically exposes properties for selection of a row element whereas you'd need to implement that yourself with messaging for the repeater.

I'd say it's mostly up to personal preference, but in your case, I would lean towards a table to start and if it doesn't feel quite right try the flex repeater.

2 Likes

See Displaying a Subview in a Table Row | Ignition User Manual.

2 Likes