Hi. What do you do with high binary sizes on iOS? I have watched this talk from Kevin Galligan from a year ago. Wondering if anybody knows anything about progress on reducing the sizes, K\N-Swift interop

Can discuss. What kind of numbers are you getting and how do you measure?

I find the binary size to be quite acceptable. My final *.ipa is <20MiB which is not bad. What's yours?

My .framework is around ~15 mb. For a pretty small sdk with a couple of standard dependencies like ktor. I am fine with that, but you know...customers complains. So I must check if there are anything to do with binary sizes. I tried "internalizing" all I could. And there were a pretty nice effect. I actually saw a reduction of ~500 kb after doing that on a bunch of data classes. Wonder if there are anything else that can help to downsize. @kpgalligan I remember you were talking about KMM team working on K\N - Swift interoperability which should reduce the size. Wondering if there are any progress on that. I read somewhere that this work was frozen.

Well, again, to measure the actual size, you need to either push it to the app store and let apples servers crunch numbers, or run local size estimates with Xcode. The size on your dev disk is not wha the actual app size will be. I don't remember how I presented it in that talk (and I have a talk today that I'm really not prepared for, so I don't have a lot of time to reply here...), but raw numbers on disk don't really tell the story. For KaMP Kit, which has ktor, sqldelight, and a few others, our sizes were ~1.5m as a final size increase on real devices. I assume local disk size was much larger, but it's been a while.

Wow, thats are really great numbers.

I would try this, if not uploading: https://developer.apple.com/documentation/xcode/reducing-your-app-s-size#Create-the-App-Size-Report

thaks. Looking into that

They're not 100% the same as uploaded, but very close.

Thank you @kpgalligan for great advise. With the help of our iOS team I was able to run the size report and results were pretty good looking. Original

~26mb

.framework file was reduced to

~6mb

. I believe it should calm down our client. However, for educational purpose I am wondering if anybody have any understanding about processes that makes this downsize actually happen. Why initial .framework is so big and how it is downsized...

I don't have a ton of detail, but there are a number of things. Debugging info, possibly multiple architectures (actual device only needs one). Probably a bunch of other stuff. It's not unique to kotlin. Ios size estimation can be complicated