ProGuard and Third Party Libraries – a Strategy

Today I tried to compile my app for release with proguard. Previously, I skipped proguard, but now I wanted a lean package :). Soon, I got into a bit of a mess, because I noticed I have quite a few libs which need custom proguard rules. So, I ended up with one proguard file per library, included in a master

My current structure, as it stands is:

My file is:

This is quite simple to manage and allows me not to modify the main file each time I have a change.

Note: Configurations for each library are already online.

A little experiment: If you find this post and ad below useful, please check the ad out :-)

One thought on “ProGuard and Third Party Libraries – a Strategy

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.

Scroll to top