I got platform native liquid glass working on my C...
# compose-ios
t
I got platform native liquid glass working on my CMP app while still keeping Compose-driven navigation. I also got it working with the compose shared element APIs despite rendering it in the interop overlay and independent of the actual compose graphics layer
🙌 7
🙌🏼 1
🔥 1
m
Nice, the problem I faced with this in
calf
library is that when you navigate back and forth from a screen A with a native nav bar to a screen B without the native nav bar, the nav bar transition isn't smooth and doesn't feel natural, otherwise it's working fine.
t
I worked around that using
movableContentOf
. Since its the same tab bar instance across screens, the tab bar maintains its state so the animation is smoother
To make it work well on a screen without, I'm going to render the nav bar on the screen that doesn't have it but offset it so its at the bottom of the screen so it looks like its animating out. Otherwise, like you said it just pops in and out
m
Ah I see nice trick. Currently I'm experimenting with a native compose navigation library with similar APIs to nav3 and just a wrapper around nav3 for all targets except iOS which provides native navigation there and wrapping each screen into a UViewController. The results are great and work fine with duo as well, hopefully it will be available in
calf
soon.
c
Wouldn't that be a blocker for ever doing a shared element though?
This is awesome to see @Tunji Dahunsi
thank you color 1
m
Yes it has some cons I'm experimenting as well to make it work with compose navigation but still facing a lot of issues with duo there.
t
What were the dup issues you were having?
I find it easier to just have each nav destination have its own nav controls instead of having wrapping UI chrome for it
d
Is it a bluesky client?
t
yup yup