I'm looking for a Compose Multiplatform Number Picker that looks like this. ( Should run on JVM &amp...

# compose-desktop

[Stefan Oltmann]

I'm looking for a Compose Multiplatform Number Picker that looks like this.
( Should run on JVM & iOS as well. )

[mohamed rejeb]

If you want this picker for all platforms, I think that @Alexander Zhirkevich has done something like this: https://github.com/alexzhirkevich/compose-cupertino

[Stefan Oltmann]

Holy... 😲

[Stefan Oltmann]

What an amazing effort.

Thank you for the link! 🙏

This could even solve my problem with the crappy original Material3 datepicker which is way to huge for small Android screens.

[Alexander Zhirkevich]

Its far from production ready. Use for your own risk. I use it for my projects and change/fix something from time to time

[Stefan Oltmann]

Thanks for making this, @Alexander Zhirkevich

I will test it and if it's stable (enough) I will use it in my production app. I take the risk. 😄

[Stefan Oltmann]

The worst that can happen is that the Composable becomes unresponsive, right? Or are there bugs that let the renderer crash?

[Alexander Zhirkevich]

Native iOS components can crash/ cause anr. Compose components should not. They can require manual migration in the future and can have visual glitches. Report if you find any

[Stefan Oltmann]

Will do.

Yes, I'm interested only in the pure Compose components. Won't need the native stuff.

[andrew]

This is separate from compose look and feel? This feels very convincing, if you put this in front of me, I probably wouldn't be able to tell it's a compose app and not an iPhone one

[Stefan Oltmann]

Personally I don’t quite get why it’s so important for some people that their iOS & Android apps look super native utilizing only Cupertino for iOS & Material for Android. It’s a lot of effort and I’m not sure about the real benefit. For Windows there aren’t even specific guidelines I know of. Yes, there is FluentUI, but honestly: How many Windows Apps look like that? 👀

Ashampoo Photos is a mix of both and looks the same on all platforms. I take the things I personally find best looking. The Cupertino date pickers look better than the material ones in my opinion, so all platforms get them.

The only exception I make in Photos is showing different icons for some specific buttons. The share button icon for example is different as users are used to different symbols for that.

[Alexander Zhirkevich]

This is separate from compose look and feel?

Not quite. Similar concept but more dedicated to iOS design language.

if you put this in front of me, I probably wouldn't be able to tell it's a compose app and not an iPhone one

This is the exact goal of this project - make pure Compose apps as much iOS-friendly as possible

[Alexander Zhirkevich]

> why it’s so important for some people that their iOS & Android apps look super native
I personally hate how material apps like Google Drive, Authenticator looks on iOS. Not the MD itself but how it differ from any other apps on my phone. Having a design system separate from MD/HIG is a solution but u still have to make your own components and as a result you'll get an app that most likely doesn't feel native both on iOS and Android.

> a mix of both
I also often mix them, there is no aim to make a 2 separate apps. Most of components like lists/chips are shared and platform-specific like alerts/app bars/ sliders/ switches are utilized as single Adaptive components so the real effort is not that big

[andrew]

Personally I don’t quite get why it’s so important for some people that their iOS & Android apps look super native utilizing only Cupertino for iOS & Material for Android.

Personally, I usually work with an in house design system that takes a lot of inspiration from material, but still can apply to iOS in a lot of ways. A library like this seems to have nice prebuilts for when you would prefer to use more system looking components for the iOS platform.