I understand that compose for iOS is in beta but is it safe to use in Prd if it compiles & builds without an issue? Or are there “easter eggs” that might popup in production (such as performance tuning mishaps, etc) that we should expect?

I have shipped some minimal use in an iOS app. The first issue I ran into was scrolling of the composable inside a popover view controller. I changed it to be a full screen VC, and that fixed that issue. The other issue I have seen, only on some devices, is switching between two composables (using a segmented control and loading/unloading compose VCs) sometimes crashes. I was not able to narrow it down, and I seem to be the only one seeing this (it could be something else in my code). So I changed that scrolling compose view into a SwiftUI version and no problem. I have maybe 3 other compose views in my app, and running very well.

Many might say those easter eggs exist for Compose UI on Android still, let alone iOS

@tylerwilson so you feel confident using compose multiplatform in PRD?

Yes, if you start small - perhaps just the content area of a view. And then test, test, test, on physical devices not just simulators (I never saw the rare crash I referred to above in a simulator).