为 UiState 数据类建模
用一个状态对象表示整个屏幕。
为 UiState 数据类建模 是 CoddyKit 上的免费 Jetpack Compose Academy 课时。 这是第 3 节课，共 4 节。 你可以在下方免费阅读本课时的完整内容 — 然后在浏览器中使用内置代码编辑器和全天候 AI 导师进行实践。 这是 Jetpack Compose Academy 学习路径的一部分，你的进度在网页和 CoddyKit 应用中同步。 Jetpack Compose Academy 课程共包含 4 节课。
本课时的部分内容尚未翻译，以英文显示。
One Object for the Screen
Instead of juggling many separate fields, model the whole screen with a single UiState data class that describes exactly what to draw.
data class ProfileUiState(
val name: String = "",
val isLoading: Boolean = false
)Why One State Object
Grouping fields together prevents impossible combinations and makes the UI a pure function of one value: same state in, same screen out.
Make It Immutable
Use val properties so a UiState can never be mutated in place. You always produce a new state, which keeps Compose updates predictable.
Updating With copy
Data classes give you copy() for free, so you can build the next state by changing only the fields that differ.
val next = state.copy(isLoading = false)Modeling Loading
Capture progress with a flag like isLoading so the UI can show a spinner while work runs, all from the same state object.
Modeling Errors
Add a nullable errorMessage field. When it is non-null, the screen shows the error; when null, everything is fine. ⚠️
data class UiState(
val items: List<Item> = emptyList(),
val errorMessage: String? = null
)Sealed Classes for Phases
For mutually exclusive phases, a sealed hierarchy is cleaner: Loading, Success, and Error become distinct types you handle exhaustively.
sealed interface UiState {
object Loading : UiState
data class Success(val data: List<Item>) : UiState
}Sensible Defaults
Give every property a default value so the initial state is one easy expression and new screens start in a clean, known condition.
private val _state = MutableStateFlow(ProfileUiState())Exposing It Read-Only
Hold a mutable state inside the ViewModel but expose it as a read-only type, so only the ViewModel may change the screen’s state.
val state: StateFlow<ProfileUiState> = _state.asStateFlow()Rendering From It
Your Composable reads one UiState and branches on its fields. The render logic stays tiny because the state already says what to show.
Single Source of Truth
A UiState class becomes the single source of truth for the screen, so your UI and logic can never quietly drift out of sync. ✨
Quick Check
Test your modeling instincts for screen state.
Recap
Model the screen with one immutable UiState data class, update it with copy(), expose it read-only, and let the UI render purely from that single source.
常见问题解答
「为 UiState 数据类建模」课时是免费的吗？
是的 — 「为 UiState 数据类建模」的完整文本可在网页上免费阅读。要进行交互式练习（内置代码编辑器和全天候 AI 导师）并解锁 Jetpack Compose Academy 课程的其余内容，请升级到 CoddyKit PRO。 Jetpack Compose Academy 课程共包含 4 节课。
「为 UiState 数据类建模」这节课中我会学到什么？
用一个状态对象表示整个屏幕。 你通过在浏览器中直接运行的动手代码来练习 Jetpack Compose Academy，全天候 AI 导师会在你学习这节课的过程中回答你的问题。
学习 Jetpack Compose Academy 需要有经验吗？
无需任何先前经验。CoddyKit 上的 Jetpack Compose Academy 课程适合初学者到高级学习者，你可以从这里开始或从头开始，按照自己的节奏学习。 这是第 3 节课，共 4 节。
「为 UiState 数据类建模」课时需要多长时间？
大多数 CoddyKit 课程大约需要 5–10 分钟。每节课都很精短且互动，所以你能稳步进步，并在网页和应用中从离开的地方继续。
我能在这节 Jetpack Compose Academy 课中编写并运行代码吗？
能。每节 Jetpack Compose Academy 课都包含内置代码编辑器，你可以在浏览器中直接编写并运行真实代码，并获得即时 AI 反馈 — 无需本地设置。