简洁地封装原生 SDK
通过 expect/actual 隐藏仅限 iOS 的 SDK
简洁地封装原生 SDK 是 CoddyKit 上的免费 Kotlin Multiplatform Academy 课时。 这是第 4 节课，共 4 节。 你可以在下方免费阅读本课时的完整内容 — 然后在浏览器中使用内置代码编辑器和全天候 AI 导师进行实践。 这是 Kotlin Multiplatform Academy 学习路径的一部分，你的进度在网页和 CoddyKit 应用中同步。 Kotlin Multiplatform Academy 课程共包含 4 节课。
本课时的部分内容尚未翻译，以英文显示。
The Native SDK Problem
Some features only ship as an iOS-only SDK, like a payment or analytics kit. You still want one shared API your whole app can call. 🎁
Define the Contract First
Start in commonMain with a tiny interface describing what you need, in your own words, not the vendor SDK terms.
interface Analytics {
fun track(event: String)
}expect the Shape
Declare an expect way to obtain that interface. commonMain promises an implementation exists without knowing how it is built per platform.
expect fun analytics(): Analyticsactual on iOS
In iosMain provide the actual that forwards to the native SDK. This is the only place the vendor framework is ever imported.
actual fun analytics(): Analytics = IosAnalytics()Adapt, Do Not Expose
Your iOS class is an adapter: it translates your clean calls into the SDK calls. The rest of the app never sees the vendor types.
A Stub for Android
If the SDK is iOS-only, androidMain still needs an actual. Provide a no-op or an Android equivalent so the app compiles everywhere.
Speak Your Domain Language
Name methods after your app, not the SDK. track and identify read better than the vendor names, and they shield you from future renames.
Swap Vendors Without Pain
Because callers depend on your interface, replacing the SDK means rewriting one adapter. Shared code does not change at all. ✨
Easier Testing
A small interface is easy to fake. In tests you provide a fake Analytics and assert it was called, with no real SDK involved.
class FakeAnalytics : Analytics {
val events = mutableListOf<String>()
}Inject the Implementation
Hand the chosen actual to your code through Koin or a factory. Injection keeps construction in one spot and the rest decoupled.
One SDK, One Wrapper
Keep a single wrapper per native SDK. That boundary is where platform mess stays, leaving the rest of your shared code clean and portable.
Quick Check
A quick check on isolating an iOS-only SDK.
Recap: Wrap a Native SDK
You learned to define a clean shared interface, provide actuals per platform, and keep the vendor SDK behind one adapter you can swap or fake. 🎉
常见问题解答
「简洁地封装原生 SDK」课时是免费的吗？
是的 — 「简洁地封装原生 SDK」的完整文本可在网页上免费阅读。要进行交互式练习（内置代码编辑器和全天候 AI 导师）并解锁 Kotlin Multiplatform Academy 课程的其余内容，请升级到 CoddyKit PRO。 Kotlin Multiplatform Academy 课程共包含 4 节课。
「简洁地封装原生 SDK」这节课中我会学到什么？
通过 expect/actual 隐藏仅限 iOS 的 SDK 你通过在浏览器中直接运行的动手代码来练习 Kotlin Multiplatform Academy，全天候 AI 导师会在你学习这节课的过程中回答你的问题。
学习 Kotlin Multiplatform Academy 需要有经验吗？
无需任何先前经验。CoddyKit 上的 Kotlin Multiplatform Academy 课程适合初学者到高级学习者，你可以从这里开始或从头开始，按照自己的节奏学习。 这是第 4 节课，共 4 节。
「简洁地封装原生 SDK」课时需要多长时间？
大多数 CoddyKit 课程大约需要 5–10 分钟。每节课都很精短且互动，所以你能稳步进步，并在网页和应用中从离开的地方继续。
我能在这节 Kotlin Multiplatform Academy 课中编写并运行代码吗？
能。每节 Kotlin Multiplatform Academy 课都包含内置代码编辑器，你可以在浏览器中直接编写并运行真实代码，并获得即时 AI 反馈 — 无需本地设置。