Is there any reason not to kick off a coroutine in...
# mvikotlins
Seth Madison
10/29/2024, 5:49 PMIs there any reason not to kick off a coroutine in a renderer so that we can do the rendering work on a background thread? (cc @Casey Morris)
Seth Madison
10/29/2024, 5:50 PMThis is a case where our renderer is just producing a ui model that the ui later consumes.
a
Arkadii Ivanov
10/29/2024, 5:55 PMWhat's renderer? You mean ViewRenderer?
s
Seth Madison
10/29/2024, 5:57 PMYes indeed
a
Arkadii Ivanov
10/29/2024, 6:06 PMWell, ViewRenderer is supposed to update the UI, so it should be running on the UI thread. This is valid for Android Views, Swing, UIKit, etc.
Arkadii Ivanov
10/29/2024, 6:10 PMOverall, all MVIKotlin components are running on the UI thread by design.
There are two primary reasons for that:
1. To prevent difficult to debug race conditions.
2. To allow the UI state changes to reach the UI synchronously on the same call stack. E.g. if an intent is sent on button click or text change, then the new state should reach the UI on the same call stack.
All heavy operations should be off-loaded in the Executor.
3 Views