I read coroutines dont work well, so network model...
# kotlin-nativeu
ursus
10/08/2019, 9:12 AMI read coroutines dont work well, so network models maybe? But I need to switch to kotlin-serialization correct?
r
ribesg
10/08/2019, 9:27 AMDepends on what you mean by “common with iOS”. As long as you don’t expose coroutines to Swift, they work well
ribesg
10/08/2019, 9:28 AMWe basically share the entire Model layer from the MVP model between apps, using data classes, ktor-client and kotlinx.serialization
ribesg
10/08/2019, 9:29 AMSome also share the Presenter layer, which is a very good idea if you have actually identical views on different platforms
u
ursus
10/08/2019, 4:35 PMhow do you share presenters that dont use any coroutines or rx? one of them is almost always present in my "components" in the domain, i.e. class that holds its own state, mutator methods and getters as observables
j
Jeremy
10/08/2019, 9:15 PMIts fairly easy to make an observable interface and provide abstractions around async work that is implemented on each platform
Jeremy
10/08/2019, 9:17 PMObservable is just a pattern, doesn't require RxJava
u
ursus
10/09/2019, 12:51 AMtrue but that either means ist the end of that chain, or reimplement (interfaces) operators
j
Jeremy
10/09/2019, 5:15 PMYes, you may want to look at reaktive
u
ursus
10/09/2019, 5:47 PMThey work with ios no problem?
j
Jeremy
10/09/2019, 6:40 PMI have only done basic analysis w/ the lib but it provides a subset of RxJava functionality and interop with similar interface. Might be worth looking into for your use case
Jeremy
10/09/2019, 6:40 PMJeremy
10/09/2019, 6:42 PMPersonally I've been trying to keep api surface between platforms as simple as possible and exposing only basic callbacks to platform via Presenter
Jeremy
10/09/2019, 6:46 PMI'm interested in different architectural patterns though. Try it out though, let us know experience. For science 🔬
2 Views