<?xml version="1.0" encoding="UTF-8"?><oembed><type>video</type><version>1.0</version><html>&lt;iframe src=&quot;https://www.loom.com/embed/0259156c54b14a4786f8b94cf318367d&quot; frameborder=&quot;0&quot; width=&quot;3840&quot; height=&quot;2880&quot; webkitallowfullscreen mozallowfullscreen allowfullscreen&gt;&lt;/iframe&gt;</html><height>2880</height><width>3840</width><provider_name>Loom</provider_name><provider_url>https://www.loom.com</provider_url><thumbnail_height>2880</thumbnail_height><thumbnail_width>3840</thumbnail_width><thumbnail_url>https://cdn.loom.com/sessions/thumbnails/0259156c54b14a4786f8b94cf318367d-4e86fafda82a04a6.gif</thumbnail_url><duration>710.043</duration><title>Net new design system component creation process: Segmented Control</title><description>This Loom explains how to create a new standardized design system component, using a segmented control as the example. The team found many existing components that served the same purpose but were coded and styled differently, with some not following the PDL and others not accessible, so they set out to standardize closely related choices that affect object state or view. Mira describes researching other design systems such as Material, Polaris, Atlassian, Lightning, and sometimes Apple, then defining guidance like limiting to a maximum number of options and not mixing content types, as well as keyboard interactions and focus states. She also references borrowing styles from similar internal components including ActionChip, Button, and ToggleSwitch, and begins visual explorations based on both external inspiration and internal variants.</description></oembed>