App Quality Dashboard


3.9 / 5

Chhi Score

This app is performing




Medium Risk










  • Install time: Icon 15.23 Sec
  • Launch time: Icon 12.53 Sec
  • Application size: Icon 5.67 MB
  • Last tested on : 27/04/2017
  • Build ID
    :   v4.0.3.5
  • Chhi Score
    :   3.9
  • Change Rate
    :   +2.63 %

What to fix?

3 Risk(s) are due to Threads in CPU exceeding the threshold.

Do not initialize objects that aren't necessary during launch times. Moving to singleton pattern helps

Build v4.0.3.3 did better in CPU . Spikes in CPU contributed to score drop by 27.03%

3 Risk(s) are due to App PSS in Memory exceeding the threshold. See how to optimize memory and remove 3 High Risk(s).

Test more often so that you don't break the CPU handling further in your next builds. CPU Score is in danger zone. Heavy battery consumption expected.

Consider re-merging the code from build v4.0.3.3, CPU score was 3.7

Utilization of CPU is close to the threshold.

The app took 12.53 seconds to load on Android OS version 5.0.2. Usually anything more than 3.2 seconds results in user drops. View details

The app has a high performance risk for the phone manufacturer(s) Lenovo, Motorola, Karbonn, Micromax. Check coverage report for more details.

5 tests need immediate attention. View performance graph.

Testability: Providing login / sign-up details could very well improve depth of bot clicks

Printing logs on callbacks would make debugging easy for tests run in our platform

Avoid wake-locks in background, using Batch and schedulers APIs such as GCM, Job schedulers could reduce wake-locks

Fix Oncreate() if the launch time is exceeding more than 3.2 secs. Try deflating views and layouts to optimize.

135.39 MB of App Dalvik utilized by activity in.coupondunia.androidapp.activities.CashbackOnboardingActivity. View details

Follow simple UI hierarchy by reducing nested layouts to Relative layouts.

Upload APKs with and without 3rd Party SDKs to monitor and optimize the impact of app performance

There is high probability of identifying risks running the apps with conditions

Caching: Use LruCache for data caching to optimize memory usage

Below 10 MB approach would increase app installs in crowded markets such as India, China and Russia!

Fix & Optimize launch time using Flatbuffers for storage and rendering performance.

Do not initialize objects that aren't necessary during launch times. Moving to singleton pattern helps

Coverage: Android version coverage for reports will range between 5.1.1 to 7.1.2

Optimize the app to render elements at 60 FPS for buttery smooth experience.

The app's Memory score has improved by 10.81% compared to build v4.0.3.3! Good job!

The app's Network score has improved by 4.44% compared to build v4.0.3.3! Good job!

Well done, Network consumption has come down by 32.33 % compared to build v4.0.3.3

Screen coverage

competition benchmark

This app is ranked #464 in Lifestyle