I'm reading the `liquid glass` blog post <https:/...
# multiplatform
u
I'm reading the
liquid glass
blog post https://kotlinlang.org/docs/multiplatform/ios-liquid-glass.html#add-navigation-callbacks-to-the-ios-entry-point and I'm not clear Does it mean compose can not know about such native liquid glassy control? Also, composeview per screen, to have swiftui own navigation - doesnt that defeat the purpose of CMP app, i.e. to "write once"?
s
Yes, it does but the native system default liquid class behavior comes with SwiftUI and Compose just cannot render it because it uses a Skia, right? We have to have these two navigation systems work together. I'm also working on it for the last five days, and it's tripping my smol brain
u
What about Flutter? I think theyre workring on it, do we know if theyll try to use the real stuff or mimicing the effect in skia?
s
I've no idea actually about Flutter
u
Im only mentioning because theyll have the same probpem
👀 1
s
But what I am currently facing is an architectural problem: putting a top bar consistently for all these screens. I have to support SwiftUI and Compose Navigation and listen to the values from the view model of Compose Common Main in SwiftUI. I have no idea what I am doing. I am just trying to understand.
By the way, do you know how to read values from the view model in SwiftUI?
u
not really in KMP youd pass the swiftui view the viewmodel reference and observe the state as async sequence
s
can you share some reference link?