App Quality Dashboard

Engage 24x7

3.6 / 5

Chhi Score

This app is performing


Medium Risk


Medium Risk




Medium Risk






  • Install time: Icon 12.50 Sec
  • Launch time: Icon 0.41 Sec
  • Application size: Icon 10.33 MB
  • Last tested on : 14/05/2017
  • Build ID
    :   v1.5
  • Chhi Score
    :   3.6
  • Change Rate
    :   -12.2 %

What to fix?

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.

Fixing CPU risks could drastically improve Chhi Score. There are 3 CPU risks.

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

Build v1.3 did better in Memory . Spikes in Memory contributed to score drop by 17.07%

Build v1.3 did better in CPU . Spikes in CPU contributed to score drop by 41.46%

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

Consider re-merging the code from build v1.3, Memory score was 4.1

Utilization of CPU is close to the threshold.

Consider re-merging the code from build v1.3, CPU score was 4.1

3 tests need immediate attention. View performance graph.

Build v1.3 did better in Network . Spikes in Network contributed to score drop by 20.41%

Caching: Use LruCache for data caching to optimize memory usage

41.94 MB of App Dalvik utilized by activity View details

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

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

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

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

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

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

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

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

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

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

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

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

Your average App Dalvik usage surged by 30.37%, Your memory score is 3.4

competition benchmark

This app is ranked #581 in Business