Design Systems

Defining Component Conventions for iOS 26

What I did

  • Led the audit of affected components
  • Defined cross-platform rules with iOS and Android engineers
  • Updated the cross-platform Figma library

Delivery

297+Instances Updated Across iOS and Android

Health2Sync iOS 26 components and screens laid out together, from dialogs and menus to the tab bar

Preparing for iOS 26

With iOS 26 introducing a new design language, Health2Sync was using a temporary switch to preserve its existing design. The team wanted to prepare for the transition before that option was no longer available.

Legacy components on the left and iOS 26 components on the right, linked by a switch turning off

Revisiting Legacy Workarounds

The app has always balanced native platform conventions with its own design identity. Preparing for iOS 26 meant more than adopting a new style. We also had to revisit designs that had been built in different ways over time.

Audit of six dialogs in the app, built in four styles with different backgrounds, corner radii and buttons

Deciding at the Component Level

We made decisions at the component level, based on what each component was meant to do. Dialogs, for example, were split into two types: basic dialogs for simple text messages adopted the native Liquid Glass style, while custom dialogs were kept for special layouts or moments that needed to reflect the brand.

Dialogs across the app sorted into two types: basic dialogs use native Liquid Glass, custom dialogs keep a branded layout

One System, Two Platforms

We turned these decisions into shared rules that let each platform keep its own style. I built them into our Figma library with Variables, so designers could switch a design between iOS and Android without starting over. The rules guided 297+ instance updates and now serve as a reference for future features.