Default parameter configuration for debug and release modes in Android Studio

The possible properties and their default values are:

debuggable: Indicates whether the program can be debugged on the phone. In Eclipse, only android:debuggable= "true" will allow us to debug the Android program on the phone. But when we do not set its Debug property in Androidmanifest.xml: When you use Eclipse to run this way, its Debug property is True when it is packaged. The Debug property of this method of using eclipse export is false when it is packaged. When using ant packaging, its value depends on whether the ant's packaging parameters are release or Debug. So it's best not to set up Android in Androidmainifest.xml: The Debuggable property is set, but it is packaged to determine its value. 

The Zipalign:android SDK includes a "zipalign" tool that optimizes packaged applications. Run Zipalign on your application to make the interaction between Android and the application more efficient at run time. As a result, this approach allows applications and the entire system to run faster. We strongly recommend using the Zipalign tool on new and published programs to get an optimized version-even if your program was developed under an older version of Android.

Runproguard: Whether the code is confusing or not proguard is a free tool for compressing, optimizing, and confusing Java bytecode files, which can remove useless classes, fields, methods, and properties. You can delete unused annotations to maximize the optimization of bytecode files. It can also use short, meaningless names to rename existing classes, fields, methods, and properties.

Default parameter configuration for debug and release modes in Android Studio