0Pricing
Kotlin Multiplatform Academy · 课时

获取各目标平台的名称

为 Android 和 iOS 编写经典的 expect/actual 函数

获取各目标平台的名称 是 CoddyKit 上的免费 Kotlin Multiplatform Academy 课时。 这是第 2 节课,共 4 节。 你可以在下方免费阅读本课时的完整内容 — 然后在浏览器中使用内置代码编辑器和全天候 AI 导师进行实践。 这是 Kotlin Multiplatform Academy 学习路径的一部分,你的进度在网页和 CoddyKit 应用中同步。 Kotlin Multiplatform Academy 课程共包含 4 节课。

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

The Hello World of KMP

Returning the platform name is the classic first expect/actual you write. It proves your shared module really runs on both apps. 👋

Declare the expect

Start in commonMain with an expect function that returns a String. No body yet, just the shape both platforms agree on.

expect fun platform(): String

The Android actual

In androidMain, provide the actual using Android's Build class to report the Android version at runtime.

actual fun platform(): String =
  "Android " + Build.VERSION.SDK_INT

The iOS actual

In iosMain, the actual reaches into Apple's UIKit to read the device's system name and version.

actual fun platform(): String =
  UIDevice.currentDevice.systemName

Signatures Must Match

Both actuals share the exact name, parameters, and return type of the expect. One mismatch and the compiler refuses to build.

Call It from Shared Code

Now any common function can call platform() freely. It reads like normal Kotlin while the right actual runs underneath.

fun greeting() = "Hi from " + platform()

Android Sees Its Value

When the Android app calls greeting(), the compiler linked the androidMain body, so it shows the Android string.

iOS Sees Its Value

The very same call from Swift returns the iOS version instead, because the iosMain actual was compiled into that framework.

Platform Imports Stay Local

Notice that Build and UIDevice are imported only in their own source sets. Shared code never imports a platform type directly.

A Tiny Surface Area

Keep the expect small and focused. One function that returns a name is enough to bridge into each platform cleanly. ✨

Test It Early

Run both apps and print the result. Seeing two different strings confirms your expect/actual wiring works end to end.

Quick Check

Think about how the right value gets chosen.

Recap

You built the classic platform() function: one expect in commonMain, an actual in androidMain and iosMain, and matching signatures across all three. 🎉

常见问题解答

「获取各目标平台的名称」课时是免费的吗?

是的 — 「获取各目标平台的名称」的完整文本可在网页上免费阅读。要进行交互式练习(内置代码编辑器和全天候 AI 导师)并解锁 Kotlin Multiplatform Academy 课程的其余内容,请升级到 CoddyKit PRO。 Kotlin Multiplatform Academy 课程共包含 4 节课。

「获取各目标平台的名称」这节课中我会学到什么?

为 Android 和 iOS 编写经典的 expect/actual 函数 你通过在浏览器中直接运行的动手代码来练习 Kotlin Multiplatform Academy,全天候 AI 导师会在你学习这节课的过程中回答你的问题。

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

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

「获取各目标平台的名称」课时需要多长时间?

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

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

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

此课程中的所有课时

  1. 为什么存在 expect/actual
  2. 获取各目标平台的名称
  3. expect/actual 类与属性
  4. 常见错误与编译器错误
← 返回 Kotlin Multiplatform Academy