The bridge handles communicating between the compiled Swift and the Java/Kotlin environment that all Android apps are contained within. This enables your Swift to be invoked from your UI layer (such as Jetpack Compose), and also enables your Swift to call out to the Android Java SDK or any other Java/Kotlin dependencies your project may have.
The bridging is designed to work alongside SkipUI, which is the SwiftUI that is transpiled into Jetpack Compose (see https://news.ycombinator.com/item?id=41384144 and the other Skip docs). But you don't necessarily need to use our transpiled UI layer to benefit from it: any Android project can embed the compiled Swift as a dependency and call into code that is exposed through a Kotlin interface.
Happy to answer any other questions. I am the author of the article.
The rest being handled by pure translationnof language constructs?