الوحدة المشتركة مقابل وحدات التطبيق

A KMP project has two app modules plus one shared module. The shared module is the brain both apps borrow from. 🧠

The shared module is a Kotlin library, not an app. It holds logic you want to write once and reuse on Android and iOS.

The androidApp module is a normal Android app. It depends on shared and adds Android-only UI and resources on top.

The iosApp is an Xcode project. It links a framework built from shared and presents the native iOS screens.

The apps depend on shared, never the reverse. Shared code stays portable because it knows nothing about either app.

Android wires shared in with a simple Gradle dependency. Once added, every shared class is importable in Kotlin.

iOS does not use Gradle directly. Instead it imports a generated framework and calls your Kotlin from Swift.

Splitting apps from shared keeps a clear boundary: business logic in one place, platform UI in its own home.

Rule of thumb: logic, models and rules go in shared; screens, navigation and platform widgets stay in each app.

The shared module owns a build.gradle.kts that lists its targets. Each app also keeps its own build file.

The same shared module can also feed a desktop or web app later. One library, many front ends. 🚀

Let us check how the modules relate.

You met the trio: one shared brain plus an androidApp and an iosApp that depend on it. Logic in shared, UI in the apps.