استدعاء التعليمات البرمجية المشتركة من تطبيق iOS

On iOS your Kotlin compiles into a framework. Swift consumes it just like any Apple library you import into a project.

At the top of your Swift file you import the shared framework by its name, usually Shared. That single line unlocks every export.

The Kotlin compiler exposes your function through an Objective-C header. Swift then sees it as a clean, native-looking call.

Top-level Kotlin functions land on a generated Kt helper class. You call greet through that container from Swift.

Swift turns the Kotlin parameter into a named argument. That is why you write name: when you call into shared code.

Drop the returned String straight into a Text view. SwiftUI renders the greeting your shared Kotlin produced. 🍎

A Kotlin String arrives as a Swift String automatically. Simple types cross the boundary without any manual conversion.

Xcode links the framework through a build phase the wizard set up. As long as that phase runs, the import resolves.

Press Run in Xcode and choose a simulator. The greeting appears, proving Swift reached all the way into your Kotlin.

If the import is red, the framework likely was not rebuilt. Build the shared module so Xcode picks up the latest header.

iOS wrote no greeting logic either. It is purely a consumer of the exact code Android already used.

How does Swift access a top-level Kotlin function?

You imported the shared framework, called greet through its Kt helper with a named argument, and rendered it in SwiftUI. 🎉