APK Analyzer provides two sizes for each file that is packaged in your APK, as well as a whole for each "directory", including Total. These sizes do not indicate the compression that you received when creating the APK (the APK format is ZIP compatible, so you can use unzip -lv qqq.apk to learn what effect this step had on the compression of everything).
For end users, both sizes really matter. With a smaller download size, they get your application faster and spend less on a data plan. With a smaller RAR size, the APK takes up less space on the user device.
But there are a few small details to consider. Take, for example, native libraries (if your application uses NDK).
First of all, consider updating the application. The Google Chrome team found that if they do not compress the native libraries, application updates become a little less. If you multiply this gain by the number of expected application updates, this gives you a major advantage.
Secondly, if you do not compress the native libraries, you can actually reduce the disk space consumption of your application (for Android Marshmallow and higher), because then the libraries can be loaded into place without unpacking to /data/data/your.app.package/lib .
Fortunately, all this is controlled by the simple addition of an attribute:
android:extractNativeLibs="false"
in the application tag in the AndroidManifest.xml file.
The same considerations apply to assets : AssetManager can download them from the APK, without having to unpack them to disk - if the object is not compressed in the APK.
APK Analyzer will show you how Google Play will compress such resources for download.