sorta related to the above, but I think its a different question entirely. ive done compose for android and desktop a while back. shared UI code. very cool. but iOS and web did not support shared UI with compose. Did that change recently? Can I write one component library and share between ios and android?
Note that while some apps already use it in production, don't expect Compose for iOS to be ready for everything yet. Popup support exists, but isn't done yet, meaning no easy dialogs/popup boxes, text fields are iffy (I'm still on 1.2.1, so maybe a 1.3.0 dev fixed this), and I'm sure there's stuff I missed. The JetBrains team is making a lot of progress, but do expect issues right now. If you're evaluating using this in a real project, I'd honestly wait until iOS support is complete, just to fairly evaluate compose. I'd hate to see a project evaluate it at too early a stage and decide against compose because of bugs before it's ready.
c
Chris Sinco [G]
11/14/2022, 1:35 AM
I’d caution on the reference to used in production for the Droidcon app. Sure it works but it’s an experimental setting and there very clear performance differences with it and native iOS (SwiftUI)