Start making edits

[finagolfin]

Ready for edits, please add comments or submit pulls.

[finagolfin]

@marcprux, should we list some apps that are using Swift in production? @ephemer, @andriydruk, @piercifani, can we list your apps?

[piercifani]

Sure!

• Naturitas
• MediQuo

[marcprux]

should we list some apps that are using Swift in production?

Yes, I think that would go a long way to demonstrating that Swift is ready for use today on Android. Between just Naturitas (500K+ installs), MediQuo (1M+ installs), flowkey (1M+ installs), and Readdle's Spark (1M+ installs), we can safely say that Swift is in use on "millions" of Android devices already, which I think it a very powerful endorsement.

I would also like to suggest adding a reference to our open-source Showcase app as an example of a 100% Swift app that demonstrates that the Swift SDK for Android can be used to build much more than just the business logic layer, for those people who are experiencing frustration with how to get going with the technology (e.g., like jacobtechtavern).

Whether any of will be palatable to the editorial team remains to be seen. Based on past experience, there seems to be some unwritten opposition to specific mention of individual products and companies. But I think it is worth a shot at least, since otherwise we'll only be able to make abstract and vague references that people are using this stuff.

[marcprux]

I also wonder if I should work in a variation on my response to https://forums.swift.org/t/swift-for-android-vs-kotlin-multi-platform/83220/2, not necessarily focusing on KMP in particular, but instead elaborating on what it means to bridge between Kotlin/Java and Swift on Android. Let me know if that sounds valuable and I'll work on it.

[finagolfin]

I would also like to suggest adding a reference to our open-source Showcase app

Maybe a brief reference then, something like "like Skip.tools (see showcase app) and" in place of my single reference now.

elaborating on what it means to bridge between Kotlin/Java and Swift on Android.

Add that bridging copy as a commit and the app links copy as another commit, and we can always take it out later if needed. Feel free to address the KMP issue as you like, as I think people do want to know how Swift compares to KMP, and Tim did suggest that contrasting such alternatives might be useful.