# Swift GUI toolkits for Android **URL:** \ **Category:** Android\ **Tags:** android, ui, gui\ **Created:** [November 21, 2025, 12:05am UTC](https://forums.swift.org/t/swift-gui-toolkits-for-android/83337 "2025-11-21T00:05:52Z")\ **Posts on this page:** 9\ **Page:** 1
**Author:** ![Finagolfin](https://sea2.discourse-cdn.com/swift/user_avatar/forums.swift.org/finagolfin/32/34388_2.png) [@Finagolfin](https://forums.swift.org/u/Finagolfin)\ **Post date:** [November 21, 2025, 12:05am UTC](https://forums.swift.org/t/swift-gui-toolkits-for-android/83337/1 "2025-11-21T00:05:52Z")
The Android workgroup is looking into the various GUI options out there- we will not provide one ourselves or choose any single existing toolkit as official, as [we say in the draft vision doc for Android](https://github.com/swiftlang/swift-evolution/blob/807b844be42db582e434d1667fc907ae7a7a8775/visions/android.md#ui-recommendations)- and plans to curate a list of the currently used GUI toolkits, with some info on how well they work with the Swift SDK for Android. Here is what we've found so far: Open Source [UIKit-Cross-Platform](https://github.com/flowkey/UIKit-cross-platform) - probably the earliest UI toolkit for Android, in development for more than 8 years and mostly written in Swift by flowkey and @Geordie_J [FlutterSwift](https://github.com/PADL/FlutterSwift) - workgroup member @lukeh's Swift bindings to Flutter, means writing your UI in Dart [SwiftGodot](https://github.com/migueldeicaza/SwiftGodot) - @migueldeicaza's Godot bindings, may require more testing but should allow you to use its GUI controls and of course the game engine itself [AndroidSwiftUI](https://github.com/PureSwift/AndroidSwiftUI) - @ColemanCDA's port of [Tokamak](https://github.com/TokamakUI/Tokamak) for Android [SwiftCrossUI](https://swiftcrossui.dev/) - @stackotter is hard at work getting his cross-platform Swift GUI toolkit [working on Android too](https://github.com/stackotter/swift-cross-ui/issues/145), still a work in progress Closed Source [Skip.tools](https://skip.tools/) - either transpiles or compiles and bridges your existing SwiftUI code to Jetpack Compose, see their [open-source showcase app](https://github.com/skiptools/skipapp-showcase-fuse), produced by workgroup members @marcprux and Abe [SCADE](https://www.scade.io/) - @gmn and team long provided their own UI engine for Android Let us know of any more we missed, plus try them out and share how well they worked for you. 😃 ---
**Author:** ![lukeh](https://sea2.discourse-cdn.com/swift/user_avatar/forums.swift.org/lukeh/32/31648_2.png) [@lukeh](https://forums.swift.org/u/lukeh)\ **Post date:** [November 21, 2025, 2:54am UTC](https://forums.swift.org/t/swift-gui-toolkits-for-android/83337/2 "2025-11-21T02:54:31Z")
> [@Finagolfin](#): > > [FlutterSwift](https://github.com/PADL/FlutterSwift) - workgroup member @lukeh's Swift bindings to Flutter, means writing your UI in Dart I should add there’s probably been some bitrot in its use of `swift-java`, I hope to have time to fix this soon. ---
**Author:** ![marcprux](https://sea2.discourse-cdn.com/swift/user_avatar/forums.swift.org/marcprux/32/12098_2.png) [@marcprux](https://forums.swift.org/u/marcprux)\ **Post date:** [November 21, 2025, 9:00am UTC](https://forums.swift.org/t/swift-gui-toolkits-for-android/83337/3 "2025-11-21T09:00:47Z")
> [@Finagolfin](#): > > [Skip.tools](https://skip.tools/) - transpiles your existing SwiftUI code to Jetpack Compose, see their [open-source showcase app](https://github.com/skiptools/skipapp-showcase-fuse), produced by workgroup members @marcprux and Abe Quick clarification: when used alongside the Swift SDK for Android, Skip in its "Fuse" mode does not _transpile_ the SwiftUI, but rather compiles it natively. The underlying implementation _bridges_ the SwiftUI API to the equivalent Jetpack Compose native views and supporting technology like navigation and observation. ---
**Author:** ![svanimpe](https://sea2.discourse-cdn.com/swift/user_avatar/forums.swift.org/svanimpe/32/38963_2.png) [@svanimpe](https://forums.swift.org/u/svanimpe)\ **Post date:** [November 21, 2025, 11:17am UTC](https://forums.swift.org/t/swift-gui-toolkits-for-android/83337/4 "2025-11-21T11:17:18Z")
There is also [https://aparoksha.dev](https://aparoksha.dev), which is similar to SwiftCrossUI. Ideally, I’d like to see those projects join forces. An open source implementation of SwiftUI (or a subset thereof) could be amazing for Swift, not just on Android. ---
**Author:** ![Finagolfin](https://sea2.discourse-cdn.com/swift/user_avatar/forums.swift.org/finagolfin/32/34388_2.png) [@Finagolfin](https://forums.swift.org/u/Finagolfin)\ **Post date:** [November 21, 2025, 12:09pm UTC](https://forums.swift.org/t/swift-gui-toolkits-for-android/83337/5 "2025-11-21T12:09:39Z")
I am aware of it, but was unaware that it had any support for Android. You are talking about the libadwaita backend? I don't see anything firm on that C library supporting Android either, in my few web searches just now. ---
**Author:** ![zaph](https://sea2.discourse-cdn.com/swift/user_avatar/forums.swift.org/zaph/32/42892_2.png) [@zaph](https://forums.swift.org/u/zaph)\ **Post date:** [November 21, 2025, 12:27pm UTC](https://forums.swift.org/t/swift-gui-toolkits-for-android/83337/6 "2025-11-21T12:27:00Z")
Technically speaking, [aparoksha](https://git.aparoksha.dev/aparoksha/aparoksha) is the 'umbrella' backend that abstracts over libadwaita, winui and swiftui. But its most notable project is [adwaita-swift](https://git.aparoksha.dev/aparoksha/adwaita-swift). ---
**Author:** ![svanimpe](https://sea2.discourse-cdn.com/swift/user_avatar/forums.swift.org/svanimpe/32/38963_2.png) [@svanimpe](https://forums.swift.org/u/svanimpe)\ **Post date:** [November 21, 2025, 2:07pm UTC](https://forums.swift.org/t/swift-gui-toolkits-for-android/83337/7 "2025-11-21T14:07:30Z")
I don’t think it supports Android yet, but given its similarities to SwiftCrossUI, the work required to port it to Android should also be very similar. I just wanted to mention it because it’s another attempt at a cross-platform SwiftUI (that may also support Android in the future) 🙂 ---
**Author:** ![Kyle-Ye](https://sea2.discourse-cdn.com/swift/user_avatar/forums.swift.org/kyle-ye/32/19686_2.png) [@Kyle-Ye](https://forums.swift.org/u/Kyle-Ye)\ **Post date:** [November 24, 2025, 10:04am UTC](https://forums.swift.org/t/swift-gui-toolkits-for-android/83337/9 "2025-11-24T10:04:26Z")
I'd give a mention to [Shaft](https://shaft.app/). It is currently not working for Android.(Only works on macOS / Linux / Window / WASM). And Android support will be added soon. ---
**Author:** ![ColemanCDA](https://sea2.discourse-cdn.com/swift/user_avatar/forums.swift.org/colemancda/32/2454_2.png) [@ColemanCDA](https://forums.swift.org/u/ColemanCDA)\ **Post date:** [July 24, 2026, 3:34pm UTC](https://forums.swift.org/t/swift-gui-toolkits-for-android/83337/10 "2026-07-24T15:34:47Z")
I've updated AndroidSwiftUI to use Jetpack Compose instead of Android views, removed Tokamak and refactoring to use a model similar to React Native since Swift cannot directly call Compose functions. Also added support for Compose Multiplatform, with macOS demo. [GitHub - PureSwift/AndroidSwiftUI: SwiftUI for Android · GitHub](https://github.com/PureSwift/AndroidSwiftUI)