Hey everyone! We’re putting together a reference o...

# compose

[Aleksey Zamulla]

Hey everyone! We’re putting together a reference of how component behavior differs across platforms in Compose Multiplatform. We know some components don’t act quite the same everywhere — scrolling, text input, focus, gestures, you name it — and we'd like to document the ones that matter most to you.

Which platform-specific differences in CMP components have surprised you, caused confusion, or required workarounds?

We're focused on behavior discrepancies between platforms when using the same components, but we're also happy to hear about components you miss on other platforms.

[James]

Lack of scroll bars was a weird one and unexpected not to see them when opening my first CMP project (I know it’s in the backlog for mobile and hope it comes soon 🤞). Along with things like back swipe (predictive back) and not separate nav bars when moving between screens on the stack (on iOS they animate into each other). Apart from that all the out the box components just scream Android (from the ripple to the general look). 😅

I can post some more if I get time to make a bit more of a list, but those for for sure my first impressions. 😄

[James]

Other few things that I just thought of which we’ve run into:
• UIKitView’s lack of transparency for its background. Tried to make a simple wrapper for UIImageView so we can use SF Symbols but all views have a white background (found workarounds but wasn’t expecting it)
• UIKitView doesn’t pass it’s modifiers for size and/or there’s no way to get it in the UIKitView to use on whatever you’ve wrapped (or at least I haven’t found it)
• Had a play with putting a UIScrollBar in a UIKitView and then add the contents of the scroll view as a Compasable wrapped in ComposableUIViewController. This didn’t seems to render. This was early poc and I could been doing something wrong (and we abandoned it anyway as it didn’t scale for dynamic content)
Only been playing with things for a couple of weeks now, but please DM if you have any follow up questions 😅

[Aleksey Zamulla]

That's very specific, thanks! For now we're looking to cover our bases so to speak, but that's a nice set of onboarding problems to consider. I may take you up on these follow-up questions down the road.

The general Android / Material look is by design at this point, right now the focus is on iOS stability rather than look-and-feel. But that's the point, right, to be transparent with people who are considering picking up the framework.

[James]

Sounds good, anytime for the followup 🙂