Introduction: Compose UI components for iOS. Just a concept for now. Work in progress...
More: Author   ReportBugs   
Screenshot 2023-05-04 at 22 06 06 Screenshot 2023-05-04 at 22 07 36


What is done (fully or partly):

  • ✔️ Cupertino and Material3 look and feels.
  • ✔️ Adaptive widgets: navbar, toolbar, icon button, ...
  • ✔️ Material Icons / SF symbols usage based on current look and feel.
  • ✔️ Cupertino scroll overflow (currently for drag only) for lazy lists and scrollable composables
  • ✔️ Insets for iOS.
  • ✔️ Cupertino context menu.
  • ✔️ Adaptive backdrop scaffold like a Modal ViewController (pure Compose) with Cupertino look and feel
  • ✔️ Swipe back navigation (based on Precompose now)
  • ✔️ Alert dialogs, action sheet, date/time picker (native)


  • More adaptive widgets (TextField, ProgresIndicator with pull refresh and more);
  • More adaptive icons


There are 2 themes:

  • Cupertino CupertinoApplication
  • Material3 MaterialApplication.

All themes are available on all platforms. No platform widgets used. Theme can be picked automatically using AdaptiveApplication

Material3 composables have CupertinoXXX analogs. They can be used directly from any place. To pick widget automatically use AdaptiveXXX composables.


SF Symbols analogs were added for some material icons. They were imported as ImageVectors and can be accessed with SFSymbols object. To pick icon according to current theme use Icons.Default.AdaptiveXXX. Names of the SFSymbols icons match the original symbols names. Adaptive icons are named in material style (SFSymbols.Gear = Icons.Default.AdaptiveSettings inside cupertino app)

Note All SF Symbols shall be considered to be system-provided images as defined in the Xcode and Apple SDKs license agreements and are subject to the terms and conditions set forth therein. You may not use SF Symbols — or glyphs that are substantially or confusingly similar — in your app icons, logos, or any other trademark-related use. Apple reserves the right to review and, in its sole discretion, require modification or discontinuance of use of any Symbol used in violation of the foregoing restrictions, and you agree to promptly comply with any such request.


Adaptive scroll behavior can be added using adaptiveVerticalScroll and adaptiveHorizontalScroll modifiers. For lazy layouts this scroll behavior can be added using adaptiveScrollOverflow modifier.

For Cupertino look and feel these modifiers add native-looking scroll overflow (currently only for drag, not fling).


Some of WindowInsets such as navigationBars, statusBars, ime, ... are implemented in common code. Paddings can be easily added with corresponding modifiers: navigationBarsPadding, ...

Keyboard (ime) padding for iOS is implemented with animation and precicely syncronized with software keyboard.

Adaptive components such as scaffolds, navigation and top bars are already respect both iOS and Android insets.

Context menu

AdaptiveContextMenu can be used to create platform popup menu:

Screenshot 2023-05-07 at 22 03 58 Screenshot 2023-05-07 at 22 04 34

For Cupertino look and feel it is always CupertinoContextMenu that is implemented in Compose. For Material look and feel it is DropdownMenu on Android and still CupertinoContextMenu on iOS, because DropdownMenu is not implemented for iOS target.

Backdrop Scaffold

Screenshot 2023-05-08 at 19 04 50

CupertinoBackdropScaffold can be used to display front layer content as iOS Modal ViewController (implemented in pure Compose).

AdaptiveBackdropScaffold uses material BackdropScaffold with Material look and feel and CupertinoBackdropScaffold with Cupertino look and feel.

To change status bar appearance to light on iOS when modal controller appears (like a native bahavior) add this to Info.plist:


Appearance will be restored when modal controller is dismissed.

About Me
GitHub: Trinea
Facebook: Dev Tools