Do you mean stripping down as in Embedded Swift compilation mode?
1 Like
Kind of! I think there’s room for another discussion though, so I’d better stop to avoid going too OT.
Is there any plan to showcase some benchmark/metrics on the performance and memory usage improvements that Swift can offer in Android, and what will be the impact to app size when using Swift on Android?
Not that I know of, but it is a good idea. We expect good results from performance and memory usage, but app size will get worse, depending on which Swift features you use (see more info below), because unlike Swift on iOS or Java/Kotlin on Android, Swift isn't bundled with the Android OS.
I'll put together a post with some numbers in the coming months, remind me if I don't.
@Finagolfin did you find any time for this?
No, since the official SDKs are not on swift.org yet- we hope to get the trunk snapshots out soon- I didn't think it was time to start looking at those perf numbers yet. I did ask Marc briefly if there were any existing Android profilers we could use, and intend to start looking into this in the coming months.
In the meantime, I highly recommend that you and anyone else interested read about @pcifani's experience shipping Swift on Android and watch this great talk he recently gave at NSSpain 2025. 
1 Like
We do this too. I think this is the best way to do xplat.
The work we did on Android support for TBC (including ds2) was geared towards also enabling profiling. We did get the runtimes built for it. IIRC we were looking at perfetto, simpleperf, and pprof as the tooling for profiling.
1 Like
And now exactly 4 months later, we have official nightly builds of the Swift SDK for Android!
9 Likes