Shrinking a Kotlin Binary by 99.2%

If you're going to get rid of all your Kotlin std lib usages by explicitly replacing them, after inspecting the actual class files generated by the compiler, with standard Java methods (and hope that no future change will re-introduce them) and you care so much about the size of your jars, I would say you're better off simply going back to Java, perhaps using the very latest version (since you're willing to use Kotlin that shouldn't be a problem) which has lots of niceties and to me, at least, looks a lot better than using Kotlin with these kinds of hacks. Add a nullability static analysis check and you're gold.

&gt; - val old = args[0].let(::File).readText() &gt; - val new = args[1].let(::File).readText() &gt; + val old = args[0].let(Paths::get).let(Paths::readString) &gt; + val new = args[0].let(Paths::get).let(Paths::readString)<p>Missed index. 0!=1.

It used to help a lot (30-40%) to sort the class files of a librarly on canonical name before you add them to its jar. Class files contain that name, and are (typically) small. Your compression factor will grow. (maybe that trick is standard now)

any idea how to get the swift upload network traffic down?<p>My 500K objc ipa ported to swift <a href="http:&#x2F;&#x2F;mro.name&#x2F;ShaarliOS" rel="nofollow">http:&#x2F;&#x2F;mro.name&#x2F;ShaarliOS</a> now is ~8MB (OTA test ipa), ~28MB for production upload causing ~300MB traffic until finally uploaded via xcrun, taking 1h on my rural uplink.<p>Has anybody an idea how to get back to sane dimensions?

Looks like most of the size reduction was from running R8. The rest seems meaningless.