Kotlin Multiplatform Academy · 课时

在共享界面之间导航

在 Compose Multiplatform 中接入导航图

在共享界面之间导航 是 CoddyKit 上的免费 Kotlin Multiplatform Academy 课时。这是第 1 节课，共 4 节。你可以在下方免费阅读本课时的完整内容 — 然后在浏览器中使用内置代码编辑器和全天候 AI 导师进行实践。这是 Kotlin Multiplatform Academy 学习路径的一部分，你的进度在网页和 CoddyKit 应用中同步。 Kotlin Multiplatform Academy 课程共包含 4 节课。

本课时的部分内容尚未翻译，以英文显示。

More Than One Screen

Real apps have many screens: a list, a detail, a settings page. Navigation is how you move between them in shared Compose code. 🧭

One Graph for Every Platform

You define a single navigation graph in commonMain, and Android, iOS and desktop all follow the same route map.

Add the Navigation Library

Compose Multiplatform ships its own navigation-compose artifact. Add it to commonMain and the routing toolkit comes with it.

commonMain.dependencies {
    implementation(libs.navigation.compose)
}

Screens Are Just Routes

Each destination is identified by a route string. Think of it like a tiny address for one screen in your app.

Create the NavController

A NavController remembers where you are and lets you move around. You create one and hand it to your graph.

val navController = rememberNavController()

Declare the NavHost

The NavHost hosts your screens and shows whichever route is current. You give it a controller and a start destination.

NavHost(navController, startDestination = "home") {
    composable("home") { HomeScreen() }
    composable("details") { DetailsScreen() }
}

Pick a Start Destination

The startDestination is the first screen users see. It is just one of your route strings, chosen as the entry point.

Navigate Forward

To open another screen you call navigate with its route. The NavHost swaps in that destination for you.

Button(onClick = { navController.navigate("details") }) {
    Text("Open details")
}

Go Back Cleanly

Calling popBackStack returns to the previous screen. Compose tracks the history so back behaves the way users expect.

navController.popBackStack()

The Back Stack

Every screen you open is pushed onto a back stack. Going back pops the top entry, just like a stack of cards.

Shared Routing, Native Hosting

The graph is shared, but each platform still hosts it in its own entry point. One route map, two native containers. 🙂

Quick Check

Which component actually performs the move from one screen to another?

Recap: A Shared Map of Screens

You added navigation, built a NavHost with routes, and used the NavController to move forward and back. One graph, every platform. 🚀

常见问题解答

「在共享界面之间导航」课时是免费的吗？

是的 — 「在共享界面之间导航」的完整文本可在网页上免费阅读。要进行交互式练习（内置代码编辑器和全天候 AI 导师）并解锁 Kotlin Multiplatform Academy 课程的其余内容，请升级到 CoddyKit PRO。 Kotlin Multiplatform Academy 课程共包含 4 节课。

「在共享界面之间导航」这节课中我会学到什么？

在 Compose Multiplatform 中接入导航图你通过在浏览器中直接运行的动手代码来练习 Kotlin Multiplatform Academy，全天候 AI 导师会在你学习这节课的过程中回答你的问题。

学习 Kotlin Multiplatform Academy 需要有经验吗？

无需任何先前经验。CoddyKit 上的 Kotlin Multiplatform Academy 课程适合初学者到高级学习者，你可以从这里开始或从头开始，按照自己的节奏学习。这是第 1 节课，共 4 节。

「在共享界面之间导航」课时需要多长时间？

大多数 CoddyKit 课程大约需要 5–10 分钟。每节课都很精短且互动，所以你能稳步进步，并在网页和应用中从离开的地方继续。

我能在这节 Kotlin Multiplatform Academy 课中编写并运行代码吗？

能。每节 Kotlin Multiplatform Academy 课都包含内置代码编辑器，你可以在浏览器中直接编写并运行真实代码，并获得即时 AI 反馈 — 无需本地设置。

此课程中的所有课时

← 返回 Kotlin Multiplatform Academy