Flex vs Coordinate Container Performance in Embedded View

People are always confused when it comes to choosing between Flex or Coordinate Container and as a rule of thumb prefer Flex unless you have diagrams or objects overlay on top of each other

In reality, any responsive behavior that can be achieved with Flex is also can achieve with Coordinate Container but you need to use CSS a lot. (of course, it is harder).

But when it comes to the performance of loading embedded views, this is the coordinate container that always is the winner.
Following footage simulate a low-end device in Chrome. (So you can the loading race easily) As shown

From Left to Right we have a column named:

  • IOP(default table boolean)
  • PV(Flex Embedded view with only two labels)
  • 4x ALM/SP/xxx (Coordinate Embedded view with icon, label, numeric input)
    As always, even in the race of loading the embedded view, the 4 coordinate columns always load faster vs one flex container. (even flex use less objects)

flex vs Coordinate slow device2


In my case, most of the time, I will use a view with a Coordinate Container, and embed a Flex, using full coordinate container, so I have best of both world, as I have the flex, and still can use overlay.