iOS 上的主线程与后台线程
安全地将工作分派到主线程之外或主线程上
iOS 上的主线程与后台线程 是 CoddyKit 上的免费 Kotlin Multiplatform Academy 课时。 这是第 2 节课，共 4 节。 你可以在下方免费阅读本课时的完整内容 — 然后在浏览器中使用内置代码编辑器和全天候 AI 导师进行实践。 这是 Kotlin Multiplatform Academy 学习路径的一部分，你的进度在网页和 CoddyKit 应用中同步。 Kotlin Multiplatform Academy 课程共包含 4 节课。
本课时的部分内容尚未翻译，以英文显示。
Two Kinds of Work
Every app juggles two kinds of work: quick UI updates and slower jobs like network calls. Where each runs matters a lot.
The Main Thread Rule
On iOS, all UI changes must happen on the main thread. Touch it from a background thread and the app can crash or glitch.
Keep Heavy Work Off Main
Long tasks belong on a background thread so the screen stays smooth. Blocking the main thread freezes the whole interface.
Dispatchers Pick the Thread
In shared code, a dispatcher decides which thread a coroutine uses. Choosing the right one keeps work where it belongs.
withContext(Dispatchers.Default) { heavyParse() }Default for CPU Work
Use Dispatchers.Default for computation like parsing or sorting. It runs on a background pool shared across platforms.
val result = withContext(Dispatchers.Default) { compute() }Main for UI Results
Dispatchers.Main hops back to the UI thread so you can deliver results safely. On iOS that is the same main queue UIKit uses.
withContext(Dispatchers.Main) { updateState(result) }A Common Round Trip
The classic pattern is simple: do heavy work on Default, then switch to Main to publish the outcome to the UI layer.
val r = withContext(Dispatchers.Default) { load() }StateFlow Helps Here
If you expose state via StateFlow, the UI collects on the main thread itself. Your shared code can update it from anywhere.
_state.value = resultAvoid the Frozen UI
A spinning beach ball on iOS usually means the main thread is blocked. Move that work off main and the freeze disappears.
Same Pattern on Android
This main-versus-background split mirrors Android exactly. Writing it once in shared code keeps both apps responsive for free.
Pick Threads Deliberately
Always ask which thread a block needs. Being intentional about dispatchers is the simplest way to avoid threading bugs. 🧵
Quick Check
One check on threading choices.
Recap
You learned to keep heavy work on Default and publish results on Main, keeping iOS and Android smooth. 🎉
常见问题解答
「iOS 上的主线程与后台线程」课时是免费的吗？
是的 — 「iOS 上的主线程与后台线程」的完整文本可在网页上免费阅读。要进行交互式练习（内置代码编辑器和全天候 AI 导师）并解锁 Kotlin Multiplatform Academy 课程的其余内容，请升级到 CoddyKit PRO。 Kotlin Multiplatform Academy 课程共包含 4 节课。
「iOS 上的主线程与后台线程」这节课中我会学到什么？
安全地将工作分派到主线程之外或主线程上 你通过在浏览器中直接运行的动手代码来练习 Kotlin Multiplatform Academy，全天候 AI 导师会在你学习这节课的过程中回答你的问题。
学习 Kotlin Multiplatform Academy 需要有经验吗？
无需任何先前经验。CoddyKit 上的 Kotlin Multiplatform Academy 课程适合初学者到高级学习者，你可以从这里开始或从头开始，按照自己的节奏学习。 这是第 2 节课，共 4 节。
「iOS 上的主线程与后台线程」课时需要多长时间？
大多数 CoddyKit 课程大约需要 5–10 分钟。每节课都很精短且互动，所以你能稳步进步，并在网页和应用中从离开的地方继续。
我能在这节 Kotlin Multiplatform Academy 课中编写并运行代码吗？
能。每节 Kotlin Multiplatform Academy 课都包含内置代码编辑器，你可以在浏览器中直接编写并运行真实代码，并获得即时 AI 反馈 — 无需本地设置。