so we dont need anymore usecase, mapper or repository class ? Is it illogical to use the functions of the mongodb class in the repository-repositoryImpl-usecase and inject it with koin?
@@StevdzaSan a simple example, for example the jvm library for calculating BMI published in jitpack, What previously only supported JVM & Android was changed to multi-platform Kotlin
Hello! First of all, thanks a lot for the video, I really appreciate the effort. I don't know if you're familiar with "raamcosta/compose-destinations." Since it's built entirely in Kotlin, I assume it should be compatible with KMM. However, I haven't tried it yet and didn't find anything in the documentation. My question is, why did you decide to use Voyager rather than Destinations? Is it simply a matter of personal preference, or is it because we can't use Destinations in KMM? Thank you!
YES YES YES YES, I’m a big fan of mongodbRealm now called Devices; but this tutorial was a bit fast for me. I wish you can create a mini-series , even for the same app but manage two or more resources also add authentication and auto-sync. I would like to see how you impliment more than one schema. Thanks: as a suggestion: the app can handle resources like, todos (as you did) and places ( name, picture,descriptions)
Awesome tutorial man! Thank you! this was a really good intro to KMM for me, Realm DB seems interesting but not a fan of those queries prefer Room DB with the annotations handling things, also Koin seems good, wonder if DaggerHilt might ever be used for KMM though? still this was really really Awesome learn't a ton, Many Thanks Maestro!
Amazing Content well explained, thank you, Stefan. My app crashes when I change the theme of the Mobile. The error is : org.koin.core.error.KoinAppAlreadyStartedException: A Koin Application has already been started