This is what I added - probably an abuse of the Stepper 🙂 but having both the min and max on one screen felt right, especially as min < max condition is enforced. Two things I noted: • At 2s and 17s is that there is the occasional flicker of a value that isn't either ending 0 or 5, but is instead 4 or 9, before it gets corrected. Highly likely I'm doing something wrong, but I wonder if you've seen this too @Steve Bower [G]? nb. only saw this on the emulator, not on real devices. • Is it planned that the stepper can use the bezel for + and - input? (Or did I fail to configure that, but it's already possible?). (My Stepper use: https://github.com/garanj/wearwind/pull/6/files#diff-bd7e769b499a685bcb1751d4b829ca03039076cb994ee52d5086f17a441703c5 )

Regarding flicker @Michail Kulaga can you take a look please?

Would the bezel swipe be supported only on some watches like the Galaxy Watch 4, or on all watches? Or maybe WearOS version dependent?

@Garan Jenkin Most definitely this issue is related to the float math which is used inside and which is unfortunately not perfect and can cause not-precise results . https://betterprogramming.pub/why-is-0-1-0-2-not-equal-to-0-3-in-most-programming-languages-99432310d476

Any chance of adding Int support to avoid these types of issues? p.p.

Yeah @yschimke it's Todo... Soon!

@yschimke yeah, adding an Int api might be a part of solution

@louiscad It would depend on the device - if a device has a bezel (mechanical or virtual) or a rolling side button it would work and should work across all Wear OS version as Compose for Wear OS supports API 25+

So it doesn't emulate virtual bezel?

I don't think we will do virtual bezel emulation in Wear Compose. Ideally, it has to be done consistently across apps in WearOS.