What are the Native Frame Carousel configuration options ?
This article describes how the Native Frame Carousel can be displayed depending on the provided configuration and the device.
General principles
Native Frame Carousel is rendered inside Virtual Try-on interface and adapts automatically based on:
-
The number of recommended frames provided
-
Frame variants provided (color, size, lens color)
-
Device type (desktop or mobile)
-
Virtual Try-on (Fitmix) container size
Only items with all required fields are displayed. Invalid or incomplete entries are not rendered.
Layout depending on configuration
Recommended frames only

-
Displays a recommended frames section.
-
Maximum 6 frames.
-
No variant selectors displayed.
Variants only

-
No recommended section.
-
Displays selectors for each configured variant type:
-
Frame Color
-
Size
-
Lens color
-
-
Frame color selector only appears if at least two valid variants exists (active variant+another variant).
-
Other variant types appear only if at least one valid variant exists.
Recommended frames and variants

-
Recommended frames section is displayed.
-
Variant selectors are displayed for the active frame.
-
Selecting a recommended frame updates the VTO and its associated variants.
Partial or invalid data
-
Variants with missing required fields are not displayed.
-
If all variants of a type are invalid, that selector is hidden.
-
Empty sections are never rendered.
Desktop layout
-
Native Frame Carousel is positioned on the right side of the screen.
-
The canvas zone is displayed on the left.
-
The Carousel zone appears as a vertical panel.
-
Variant selectors are stacked in separate sections.
Mobile layout

-
Native Frame Carousel is positioned at the bottom of the screen.
-
The canvas zone occupies the upper area.
-
Recommended frames are displayed in horizontal scroll.
-
Variant selectors are accessible through expandable menus.
Responsive behavior
Virtual Try-on automatically switches between desktop and mobile layouts based on screen size. No additional responsive implementation is required from the integrator.