Effective ProGuard keep rules for smaller applications (Google I/O '18)

Рет қаралды 32,749

Күн бұрын

ProGuard keep rules are the super power in reducing application size. Correctly specified, they allow tools to remove unneeded code and obfuscate applications. But what exactly do these rules mean? This session provides an answer by deep diving into what happens inside the compiler based on those rules.
Rate this session by signing-in on the I/O website here → goo.gl/7UjzKa
Watch more Android sessions from I/O '18 here → goo.gl/R9L42F
See all the sessions from Google I/O '18 here → goo.gl/q1Tr8x
Subscribe to the Android Developers channel → goo.gl/GEh1ds
#io18 event: Google I/O 2018; re_ty: Publish; product: Android - Android Studio, Android - Platform; fullname: Stephan Herhut; event: Google I/O 2018;

Пікірлер: 19

@robchr 6 жыл бұрын

I liked the walk through of how to generate better keep rules.

@amirrezafiroozi4080 5 жыл бұрын

One of the best presentations I've ever watched! nicely explained!

@h4m74ro 6 жыл бұрын

Great talk! R8 shrinks already a lot more than proguard. Couldn't find any regressions until now. 😎

@amiladrck 3 жыл бұрын

Great explanation!

@witoldsienski1709 6 жыл бұрын

Great talk :)

@Maciejfw 2 жыл бұрын

Thx, this was a great video. I wish that I learned this lafter years of debuging minify randomly.

@JimmyDeemo 6 жыл бұрын

I would very much like to see some workable examples of how one should approach a similar problem, but on a much bigger application. e.g. Unity app where you utilise many plugins, the code of which is quite hidden from you, but need to try to keep it under the dex limit.

@rameshpant1204 2 жыл бұрын

Not just that, many of GOOGLE's own code base is hidden, so when I'm trying to use just firebase for cloud messaging part, I somehow need gms libraries as well (which contains ads and crash analytics libraries, I suspect which in no way is needed for my app). Stephan here was indeed lucky to not be working with firebase or GMS.

@PoPo-bi6nh 2 жыл бұрын

@BrianChu888 6 жыл бұрын

978Kb still include all these classes and layouts which this app will never use (e.g. abc_alert_* layout, v4 media class, notification layout, etc etc) and there seems to be no way to get rid of them. hope R8 will fix it.

@MrOneWorld123 4 жыл бұрын

The previous session about the compiler: kzfaq.info/get/bejne/na1_gs6cl9_Dg6c.html

@poojapatwa217 5 жыл бұрын

Here If I am setting -dontwarn to these warning I am able to build signed apk but that is not getting installed. kindly do the needful

@raespim 2 жыл бұрын

this final rules solution keepclassmembers didn't work and my app crashes.. android studio version is Artic Fox with 7.0.2 gradle plugin.... did i foget something?

@royalstranger 3 жыл бұрын

Can anyone solve this problem AAPT: unknown option '--proguard-minimal-keep-rules'. aapt2 link [options] -o arg --manifest arg files... Using build script classpath 'com.android.tools:gradle:4.0.1' Version : 6.1.1 gradle version in distribution Url

@chandanvidyarthi3660 4 жыл бұрын

Can progaurd obfuscate activity class ?

@user-pc5xz9oj6c Жыл бұрын

R8 can do obfuscate for class(simply change class name) .. to make it harder for reverse engineering... this mean its harder for any one to steal your source code and upload it in different platform like apk pure and simliar platforms.... R8 have it own programing langague (R8 language used shrink apps only )