Hi, at my company we are looking to rework our And...

# compose-ios

[Arne Vanstraeseele]

Hi, at my company we are looking to rework our Android and iOS app and are looking into the possibilities for maybe a crossplatform solution. KMP with compose looks for us a very good solution but the only concern we have is that compose iOS is still in Beta. Is there a timeline for compose iOS?

[François]

You mean Compose Multiplatform?

[Arne Vanstraeseele]

Yes Compose Multiplatform

[Richard]

My guess is, that at this years KotlinConf it will be announced as "stable".

[Arne Vanstraeseele]

especially the iOS side of it

[Arne Vanstraeseele]

That was my guess too but I can't convince my CTO to take this.

[Richard]

If you are using Android's Compose right now, there is so much "experimental" and you wouldn't be allowed to work with it either then. 🙂 Your CTO should not be afraid or wait until May.

[François]

Compose for iOS is still work in progress, there is no official iOS Look&Feel for Compose iOS and the accessibility is incomplete.

[Arne Vanstraeseele]

is there a list of the issues that are still under construction and what not? Or should I better go with kotlin multiplatform and implement the UI with jetpack compose for Android en SwiftUI for iOS?

[François]

> is there a list of the issues that are still under construction and what not?
Not sure if there is a list
> Or should I better go with kotlin multiplatform and implement the UI with jetpack compose for Android en SwiftUI for iOS?
This one is recommended way until compose is ready.
You can start to work with CMP only with Android and iOS using SwiftUI/UIKit, then switch iOS to Compose when ready.

[Richard]

recommended

Where? It's up to whomever what to use. I would argue that CMP for iOS is ready.

[François]

Compose will be ready when it will be a good remplacement of Flutter and have these ones.

[Richard]

If you want that you can use https://github.com/alexzhirkevich/compose-cupertino (or others)

[François]

Yeah, the maintainer is not active at all (and not working), someone made a fork to be up-to-date and working, it’s still unofficial.

[Csaba Szugyiczki]

Why would cupertino widget support be necessary to consider it stable, if most apps user their own design system, that is neither Material or Cupertino based

[Csaba Szugyiczki]

The moment you start to create an app that looks Material on Android and Cupertino on iOS is when you loose the benefit of writing it as a cross-platform app. It becomes a nightmare to maintain and find the common ground for both Design Systems

[Richard]

You could still do some stuff look like Android and some like iOS if you want, but for that actual/expected should be good enough. (for example some icons like sharing)

[David Nedrow]

The moment you start to create an app that looks Material on Android and Cupertino on iOS is when you loose the benefit of writing it as a cross-platform app.

So iOS should look like Material? I haven't looked at Kotlin Compose. Do they provide their own non-Material widgets?

[Cherrio LLC]

Material widgets are built ontop of the barebones compose. You can use compose without material and that’s what we’re doing. All our widgets are custom from our design system.

[François]

It just more work to do for iOS integration. An UX library like what flutter give should be available officially.

[Cherrio LLC]

Most teams already have a design system, so it’s okay to just make that multiplatform to support iOS. But for indie developers or solo ones they might care about the look and feel of native widgets.

[François]

UI can be totally customized and not linked to Cupertino. I’m talking about UX (dialog/modal/picker/…)

[Guilherme Delgado]

Compose Multiplatform's accessibility support is a critical factor in my decision to adopt it, despite JetBrains' stability claims. The European Accessibility Act, effective June 28th (see: https://legal.pwc.de/en/news/articles/the-european-accessibility-act-an-overview-what-s-changing-and-for-whom), mandates accessibility compliance. Therefore, robust accessibility features in CMP are essential for any project targeting the EU market.

[Guilherme Delgado]

And as @François stated, on iOS the accessibility is incomplete.

[Richard]

What exactly is incomplete?

[Guilherme Delgado]

2 threads above, for example, https://kotlinlang.slack.com/archives/C0346LWVBJ4/p1739896550333869

[David Nedrow]

Oooh, I see. You're saying Compose Multiplatform is incomplete regarding accessibility on iOS. I originally read your message as saying iOS' accessibility support is incomplete.