https://kotlinlang.org logo
#orbit-mvi
Title
# orbit-mvi
m

Mikolaj Leszczynski

08/05/2021, 7:12 AM
Our very own @appmattus did a review of competing MVI libraries and has come up with some interesting conclusions. Well worth a read! https://proandroiddev.com/top-android-mvi-libraries-in-2021-de1afe890f27
K 1
🔥 5
🙌 5
o

Oleksii Malovanyi

08/05/2021, 7:20 AM
to see if what Orbit does still makes sense
guys, really? 😆
m

Mikolaj Leszczynski

08/05/2021, 7:22 AM
due diligence we ignored for too long @Oleksii Malovanyi 🙂
great to see we have something unique to offer and that we’re on the right path 🙂
❤️ 1
o

Oleksii Malovanyi

08/05/2021, 7:34 AM
keep it going 👍
🙇 1
m

miqbaldc

08/06/2021, 4:00 AM
the library runs actions in sequence. So, while we may expect 
action2
 to complete first, it only starts execution once 
action1
, scheduled first, finishes
The above statement was solved by Orbit-MVI due to its support us doing a parallel decomposition cmiiw?
m

Mikolaj Leszczynski

08/06/2021, 7:44 AM
No, it’s because Orbit launches a coroutine for each intent
✍️ 1
but you still have to make sure you’re not doing blocking work on Orbit’s container thread, or it will have the same problem as Uniflow.
When it comes to suspending work though - the unit test in the article suggests that Uniflow does not seem to run separate coroutines for each intent, meaning that suspending work will block until completed - Orbit does not have that issue.
🙏 1
2 Views