PeopleInSpace VS kotlinx.coroutines

I'm already using this structure with one of my projects and I found the experience really pleasant. There are good examples of doing it, one of them being: https://github.com/joreilly/PeopleInSpace

It does work with iOS. You just have to structure it in a way that'll work well. See the People In Space repo to see how it works with iOS

I mostly walked into the setup. My team already did a lot of heavy lifting. I will try to piece together something for the structure/template. Meanwhile, lot of samples are already present here : https://kotlinlang.org/docs/multiplatform-mobile-samples.html Specially https://github.com/joreilly/PeopleInSpace

Here's a project using it.

For DI take a look at Koin. It's a pragmatic lightweight dependency injection framework for Kotlin developers with multiplatform support. PeopleInSpace sample project uses it.

You might be interested in this project https://github.com/joreilly/PeopleInSpace

Now, let's consider an example. For instance, let's create a Kotlin/JVM project with kotlinx.coroutines library as a dependency.

Greetings community, I just submited a PR to Kotlin coroutines with two additional operators :

The harder parts of Kotlin are going to be things like kotlinx.coroutines, but that's just a library, not a core part of the language. It's about as hard to learn as a comparable library in another language, like the Task Parallel Library in .NET.

Kotlin has coroutines that are supported by the language and implemented by a library (the implementation remains platform-dependent): kotlinx.coroutines and a sandbox environment is available here to try it out.

That said, since it seems like you're doing UI stuff (Android?), you're best off doing all of the UI code in coroutines, using Dispatchers.Main as a context (as provided by one of the platform-specific coroutine libraries), since this will guarantee that your UI code will be safely run in the UI thread.