marcprux

6 ms·

31.
by marcprux 1y ago
Thanks for posting this! I am the author of the post and work on skip.tools, so feel free to AMA. Hopefully this helps address many of the "what next" sorts of questions we're fielding in the Swift Android workgroup regarding
32.
by marcprux 1y ago
> the demos on your page look like impostors on Android On the Android side, Skip apps utilize Jetpack Compose directly, which is the officially recommended toolkit for creating Android apps these days ( https://developer.andro
33.
by marcprux 1y ago
The Swift SDK for Android doesn't specify or mandate any user-interface technology, but leaves it open for other projects to build upon. For example, Skip.tools re-implements SwiftUI for Android by bridging it to Jetpack Compose, so yo
34.
by marcprux 1y ago
An example of an Android app that is built using the Swift SDK for Android and is available in the Google Play Store is Skip Showcase: https://github.com/skiptools/skipapp-showcase/ (disclaimer: I work on the Skip
35.
by marcprux 1y ago
Yes, Skip has been using our preview release of the Swift SDK for Android in our Fuse mode for over a year, and it has proven to be very popular! You can see our blog post about using it to build a completely native SwiftUI app for Android
36.
Android Doesn't Deserve Swift–But We Did It Anyway [video](youtube.com)
3 points by marcprux 1y ago|1 comments
37.
by marcprux 1y ago
We wrote about what it means for F-Droid at: https://f-droid.org/en/2025/09/29/google-developer-registrat... And it has been discussed in a couple of HN threads: https://news.ycombinator.com&#
38.
by marcprux 1y ago
I do think that this very much puts Google in the same boat as Apple in terms of how the GPL is deemed compatible or not for distribution to their platforms and proprietary stores. Personally, I think that the GPL is still compatible with
39.
by marcprux 1y ago
> A small call to any googler on the thread - put your support towards this internally. Post author here. This. Google toyed with a scheme like this a few years ago and reached out to F-Droid, and they were told the chaos it would cause.
40.
by marcprux 1y ago
Post author here. I've also been in various DMA enforcement workshops and consulted with EU regulators on the topic of app distribution. The "strictly necessary and proportionate measures to … not endanger the integrity of the har
41.
How FOSS Projects Handle Legal Takedown Requests(f-droid.org)
2 points by marcprux 1y ago|0 comments
42.
by marcprux 2y ago
Are there plans to add support in your client libraries like https://github.com/supabase/supabase-swift ? And could this be used as backend support for https://github.com/drewmccormack/Forked ?
43.
by marcprux 2y ago
> My assumption is that Google has keys to everything in its kingdom If that were true, then their claims to support E2E encrypted backups are simply false, and they would have been subject to warrants to unlock backups, just like Apple
44.
by marcprux 2y ago
> you think Google didn't already sign up to this? My understanding is that Android's Google Drive backup has had an E2E encryption option for many years (they blogged about it at https://security.googleblog.com&#x2F
45.
Swift on Android Working Group (Swift.org)(forums.swift.org)
3 points by marcprux 2y ago|0 comments
46.
Swift Everywhere: Bringing Swift Packages to Android(skip.tools)
2 points by marcprux 2y ago|0 comments
47.
by marcprux 2y ago
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 enable
48.
How the development wall between Android and iOS may soon come down(androidpolice.com)
1 points by marcprux 2y ago|0 comments
49.
by marcprux 2y ago
I recently wrote about using a native Swift toolchain for Android: https://skip.tools/blog/native-swift-on-android-1/
50.
A Swift Toolchain for Android, Part 1: Setup, Compiling, Running, and Testing(skip.tools)
16 points by marcprux 2y ago|0 comments
51.
by marcprux 2y ago
Not yet, but this is a capability that we are actively investigating.
52.
by marcprux 2y ago
> given the point of this is not having to learn android We wouldn't say that is the point of using Skip. The benefit you get from using Skip is that you can use a single language and a single framework for building your app, and yo
53.
by marcprux 2y ago
> This will likely grow over time This is indeed our primary focus, now that Skip 1.0 is released. We already have a bunch of open-source frameworks that bridge common libraries like WebKit, Firebase, Lottie, SQLite, and more. We expect
54.
by marcprux 2y ago
While the core of your Skip code and resources exists in one or more Swift Package Manager module (which will be transpiled into corresponding Gradle modules), the scaffolding of your actual app is still an Xcode project on the iOS side, an
55.
by marcprux 2y ago
You are correct that JNA's C++ integration – while possible – is not exactly seamless. It is an area that we are actively researching better solutions for.
56.
by marcprux 2y ago
The Skip transpiler runs locally on every build. It is implemented as an Xcode build plugin, so it is transparent and instantaneous. Every change you make to the Swift code is immediately converted into Kotlin, so each time you launch the a
57.
by marcprux 2y ago
To put the question in context, I'll preface by saying that Skip is unique among cross-platform app development solutions in that it isn't imposing an "alien" language or runtime on your app. It uses Swift on iOS, and Ko
58.
by marcprux 2y ago
It's fast for me my on my iPhone 12 Mini (Safari) and Pixel 6 (Chrome). What device and browser are you using? Are any particular pages slower than others?
59.
by marcprux 2y ago
Glad you asked! We have an FFI framework ( https://skip.tools/docs/modules/skip-ffi/ ) that enables you to use the same native code on both iOS and Android. I wrote a blog post about it at: https://s
60.
by marcprux 2y ago
Out of curiosity, what are your existing workflows? Note that Skip doesn't put any constraints on the iOS side of your app at all: if it can be expressed with SwiftUI or UIKit, then you can do anything. If there are bits that SkipUI do

More ›