جولة في المجلدات المُنشأة

The template looks busy at first. Once you learn what each folder is for, you will always know where your code belongs. 🗺️

The shared module is the heart of KMP. The Kotlin you write here is reused by both the Android and iOS apps.

Inside shared, commonMain holds platform-independent Kotlin. Code here must compile for every target you chose.

androidMain is for shared code that needs Android-only APIs. It is your place for platform-specific actual implementations.

iosMain mirrors androidMain for the Apple side. It holds Kotlin that touches iOS-only frameworks and platform details.

The androidApp module is a normal Android project. It depends on the shared module and contains the Android UI and entry point.

The iosApp folder is an Xcode project. You open it in Xcode, and it links the framework built from your shared module.

The build.gradle.kts files configure each module. The shared one declares your targets and dependencies, so you will edit it often.

settings.gradle.kts lists which modules belong to the build. It is how Gradle knows shared and androidApp are part of one project.

gradle.properties holds project-wide flags, like JVM memory and KMP options. Small tweaks here affect the whole build.

Shared code goes in the shared module, platform UI lives in the app modules, and Gradle files glue it all together. That map carries you far.

Where should you put Kotlin code that must work on every target?

You toured the layout: the shared module with commonMain, androidMain and iosMain, the two app modules, and the Gradle files that bind them. ✅