ViewModel isn't ready to be shared yet. What we need is a data structure that both Compose and SwiftUI can recognize and observe. If we had that it would be a HUGE step forward
Loving this framework, thanks a lot! Just looking for the right way to get result of a sub navigated screen (e.g. a FriendPickerScreen) back into the previous screen/state. Any hints or an example how to achieve it?
![[#2024MAMA] ROSÉ (로제), Bruno Mars - APT. | Mnet 241122 방송](http://i.ytimg.com/vi/dgGqD28J6aQ/mqdefault.jpg)
Thanks for good and detailed explanation of this project and things like MVI, Reducers and examples of code!
ViewModel isn't ready to be shared yet. What we need is a data structure that both Compose and SwiftUI can recognize and observe. If we had that it would be a HUGE step forward
As I understand the gap is on the Swift side, right?
i think you have good understanding. You must make videos to teach us.
@@shoaibkhalid6156 but without a monthly subscription please. I'm broke ass
@@AzMahgs Mitch has a lot of free content but it takes time and investment to make videos: he needs to make money or he would be broke ass too.
What about moko mvvm livedata?
Great! I like your video😍
Loving this framework, thanks a lot! Just looking for the right way to get result of a sub navigated screen (e.g. a FriendPickerScreen) back into the previous screen/state. Any hints or an example how to achieve it?
Good Tutorial thanks