Hello guys. We are considering using compose for an upcoming utility app for our customers. To be able to successfully convince management to consider it too we need to know the limitations with the alpha version right now. Basically things that might be a blocker down the road

Do you plan to hide the fact about alpha status of Compose for iOS? 🙃 In some cases there can be performance issues (due to GC for example). I think It can be less of a problem if you would target relatively new models. Another thing is that look and feel (e.g. scroll and animation physics) have to be adjusted to be ios-like (and some users may notice it). These things will be improved in the future though. Do you plan to use UiKit interop or compose only components? I think @Dima Avdeev and @Nikita Lipsky could add a little bit more on this.

To execs alpha is a different word lol.

You might've seen already. Just in case, camera and mapview interop were used in https://github.com/JetBrains/compose-multiplatform/tree/master/examples/imageviewer

For now, the Alpha version of Compose for iOS contains some bugs. And backward compatibility is not guaranteed.

TextField has a few bugs, and I can't get TextFields working at all in a popup (haven't tried 1.4.0 stable yet). Last I checked, multitouch wasn't working but I believe that made it to the 1.4.0 release.