Запуск приложения Android из Studio

Your shared Kotlin is ready, so let's see it live. We start with Android because Android Studio drives the whole build, end to end. 🚀

The run configuration you want is the one for the androidApp module. It bundles your shared code into a real installable app.

Next to the run button is the device picker. Select a connected phone or spin up an emulator image from the dropdown.

No device handy? Open the Device Manager and create a virtual device. A recent Pixel with a modern API level is a safe default.

Hit the green Run arrow. Studio compiles the shared module, builds the APK, installs it, and launches the app for you.

Behind the scenes Gradle assembles the androidApp and pulls in your shared library as a normal dependency. Watch the Build tab for progress.

On Android there is no special bridge. Your shared module compiles to JVM bytecode and is consumed like any other Kotlin dependency.

Open Logcat to see runtime logs from both your app and shared code. It is your first stop when something behaves oddly.

Change shared logic, hit Run again, and Studio rebuilds only what changed. This tight loop keeps your feedback fast. ⚡

If the build stops, scroll to the first error in the Build tab. The earliest message usually points at the real cause.

Seeing your shared greeting on a real Android screen proves the wiring works. That confidence carries straight into the iOS run next.

You ran the app by picking androidApp, choosing a device, and pressing Run. Gradle built the shared module as a plain dependency and Logcat showed it working. 🎉