Skip.tools

Incredible news: Skip is now free and open-source for everyone! Create fully native x-platform apps in Swift and #SwiftUI, with deep Android and #JetpackCompose integration, powered by the Swift Android SDK Read more and learn how to contribute: skip.dev/blog/skip-is-f…

Skip has a new site and new socials! Update your bookmarks to keep up with the latest Swift on Android developments: skip.dev @skiptools@mas.to Goodbye X. We hope to see you on Mastodon, and as always: Happy Skipping!

In case you missed it: Fantastic presentation at NSSpain on using the Swift Android SDK + Skip to share business logic in a real-world app. And it’s even easier today! “Android Doesn’t Deserve Swift—But We Did It Anyway — Pierluigi Cifani” youtube.com/watch?v=EIGl6G…

Today’s user contribution: view modifiers! These add Android support for several new #SwiftUI view modifiers Recall: SkipUI transpiles to Kotlin and interacts with #JetpackCompose: github.com/skiptools/skip… SkipFuseUI bridges to compiled Swift on Android: github.com/skiptools/skip…

Skip’s new getting started guide makes it easier than ever to try the Swift Android SDK. Whether you’re sharing some business logic or creating an entire dual-platform #SwiftUI app, setup is just a few steps: skip.tools/docs/gettingst…

When you use Swift on Android, you can truly use the entire Swift language. But when you want some Swift to talk to Android #Kotlin APIs and vice versa, what @swiftlang features can be bridged? With Skip, more than you might think! skip.tools/docs/bridging/

Our PR to enable URLSession.websocketTask on Android has merged! Skip long supported WebSocket in transpiled mode. But customers quickly found it missing when using compiled Swift @swiftlang Use ‘skip android sdk —help’ for help getting the 6.3 nightly github.com/swiftlang/swif…

Today’s user contribution: Android support for #SwiftUI ViewThatFits! UI patches are in 2 parts. SkipUI transpiles to Kotlin & interacts with #JetpackCompose: github.com/skiptools/skip… SkipFuseUI is compiled Swift on Android and bridges to SkipUI: github.com/skiptools/skip… Enjoy!

2025 was a banner year for Swift on Android. With simple tooling, deep Android integration, and #SwiftUI + #JetpackCompose support, Skip turns this tech into a robust platform for x-platform mobile dev. Read our 2025 retrospective and look forward to 2026: skip.tools/blog/skip-2026/

Black Friday special! Through the weekend, all Skip.tools subscriptions are 50% off. Just enter the code `BLACKFRIDAY2025` on the Skip subscription page. There's never been a better time to give Skip a try and bring your SwiftUI app to the entire iOS+Android market!

@jacobtechtavern @dean_lusk The cool thing is that Skip makes your Swift @Observables “just work” to power Jetpack Compose. So it’s a lot easier to do your view models in Swift Of course Skip also supports SwiftUI for Android, but there are lots of reasons you might use Compose for some or all of your UI

@dean_lusk Someone on the skip team gave my piece a proof read! I kept it out of scope for here but I hear it makes life a lot easier

The biggest question when using Swift for Android: “Where do the view models go?” This is the single most controversial point of debate when implementing a multiplatform solution*. Where do we put the view models? *I guess nowadays it’ll be a distant second, after “Are we using Kotlin or Swift?” “Shared business logic” unambiguously includes networking, caching, analytics, models, processing, queues, config, and most of your services. But view models (and, depending on your architecture, perhaps interactors, presenters, and navigators) could go either way. This is a double-edged sword. If you put all these in the shared multiplatform libraries, you’ll potentially increase the percentage of shared code from ~50% to ~80%. But, if you choose to share these, you’re also going to be fighting (at least) one of the systems at some point. SwiftUI expects @Observable view models. Jetpack Compose prefers StateFlows. If you go down this route, you’ll go insane unless you use some kind of wrapper library like KMP-ObservableViewModelas a shim to make code work on the non-native platform. I have absolutely no clue about the performance implications of this, other than that it’s not zero. I made life easier for myself and kept the view models on the native side. Read my full analysis, Swift Android vs Kotlin Multiplatform, here 🚀 blog.jacobstechtavern.com/p/swift-for-an…

Excited to announce that Skip Fuse is now free for Indie developers! Now you can use the new official Swift SDK for Android to build your whole app in native Swift! Rea about it at skip.tools/blog/skip-fuse…

You can read our reflections on this development at skip.tools/blog/official-…

We are thrilled to announce that the Swift SDK for Android is now an official and supported part of the Swift project! This grants a huge amount of confidence to those who may have been hesitant about Skip's approach of bringing SwiftUI to Android. #swiftui #androiddev #iosdev

Big news for Skip and Swift on Android! We're proud to be founding members of the Swift Android Workgroup and finally seeing an official release!

Fantastic presentation at @NSSpain last week on using Skip along with the Swift Android SDK to seamlessly bridge between Kotlin and Swift in a real-world project. “Android Doesn’t Deserve Swift—But We Did It Anyway” youtube.com/watch?v=EIGl6G… #iosdev #swiftui #androiddev

There is much more to Skip than just #SwiftUI and #JetpackCompose: there is a whole suite of optional modules that you can add to your project that provide additional integrations with the underlying platform. skip.tools/blog/showcase-…

Marc from skip.tools was just interviewed on the Swift Package Indexing podcast about the Swift Android Workgroup and other Swift/Android topics. Check it out at skip.tools/blog/skip-on-s…