Add preRelease build type to distribute release build with Chucker

[hoangnguyen92dn]

Why

As of now, many applications are being built with Compose UI. Besides the efficiency of using Compose, there is a noticeable issue in the app performance. This performance issue is not only in the implementation-wise; the Compose framework itself causes lagginess in the debug build.

The main purpose of distributing the debug build is to enable Chucker logs for Project Managers/Testers to perform Quality Assurance on backend tasks and investigate API issues during app testing.

📚 Following the best practice guideline, enabling the release build to boost the app performance

🙋 Question!? Then how the PM/Tester verify the API request and response with Chucker?

💡 Solution:

Creating a new build type in the middle of release and debug build that called preRelease:

Release <-> PreRelease <-> Debug

🍀 The further benefits of applying the preRelease build type is to detecting issue on release build such as code obfuscation with Proguard as soon as possible to avoid crashes.

Who Benefits?

Developers, PMs

[luongvo]

@ryan-conway @hoangnguyen92dn This should be a higher priority as well. Please plan for it 🙏