Yes, Skip is a major contributor to this effort!

Are they putting work into the SDK or is there some integration going on? The way I understand it the SDK is compiled straight into Android binaries, whereas Skip transpiles? How does that work together?

Metal cannot be used on Android. Your business logic can be ported - if it's separated as a library. If you don't want to separate it, Skip can handle bridging a lot of Apple libraries including SwiftUI.

Thanks - I see, so swift packages for everything.

What would be the equivalent shader / GPU language on Android? OpenGL?

OpenGL or Vulkan, you might be able to have some luck transpiling metal shaders to spirv-cross at a cursory look

Sometimes it is easiest to have an agent like Codex rewrite the shader instead...

Vulkan with glsl to spirv compiler would be equivalent

I'm pretty happy with that number, considering this ecosystem is _brand new_. This is the lowest it'll be.

Yes and any package dealing with UI is automatically disqualified, so 25% really is pretty good.

The post doesn't display Xcode but Android Studio. While with Skip you can build & run through Xcode, that's not something we support right now.

You can build the Swift part in Xcode, VSCode or your favorite editor. But the Android builds don't work with Xcode today.

Isn't it kinda a bad sign that people on HN have to argue in comments about what your library/framework/sdk even does?

The SDK doesn't quite work that way, your iOS-specific dependencies like SwiftUI and UIKit aren't available. For SwiftUI development, [Skip](https://skip.tools/) has a transpiler that translates your SwiftUI code into Jetpack Compose.

Without Skip, you can still share other code through JNI - similar to Kotlin Multiplatform.