我想在协程中改进我的async-await。这是我的解决方案

val coroutineContext: CoroutineContext
        get() = job + Dispatchers.IO
[...]
            lifecycleScope.launch(coroutineContext) {
                async {
                    client = viewModel.getClientItem(clientId)
                }.await()
                if (inEditMode != null) {
                    changedEditMode = true
                }
[...]

@马尔科·托Perl尼克在Why does this coroutine block UI Thread?中写道

Note: this post dates back to the pre-release version of coroutines. I updated the names of dispatchers to match the release version.
runBlocking is not the way to start a coroutine on the UI thread because, as its name says, it will block the hosting thread until the coroutine is done. You have to launch it in the Main context and then switch to the Default context for the heavyweight operation. You should also drop the async-await pair and use withContext:
button1.setOnClickListener {
    launch(Main) {
        withContext(Default) {
            Thread.sleep(5000L)
        }
        textView1.text = "Done! UI was not blocked :-)"
    }
}
withContext will suspend the coroutine until done and then resume it in the parent context, which is Main.

为什么先用主调度器，然后用默认调度器，这样做比异步更好。它也会阻塞主线程，工作方式相同。区别是什么？如何处理这种方法？
问候语
编辑：我的另一个解决方案是下面的这个或withContext(Dispatchers.IO)

lifecycleScope.launch(Dispatchers.Main) {
                withContext(Dispatchers.Default) {
                    client = viewModel.getItem(clientId)
                }
[...]
}

现在我读到我没有使用runBlocking，也没有阻塞主线程。在这种配置下，它的工作原理和async-await一样。你认为这是更好的解决方案吗？