App Quality Dashboard


4.0 / 5

Chhi Score

This app is performing


Medium Risk


Medium Risk










  • Install time: Icon 21.20 Sec
  • Launch time: Icon 0.66 Sec
  • Application size: Icon 10.42 MB
  • Last tested on : 25/04/2017
  • Build ID
    :   v4.1.13
  • Chhi Score
    :   4.0
  • Change Rate
    :   -4.76 %

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.

App launch time went up by 54.17% initlizate network calls after few seconds of loading the resources. View details

Build v4.0.11 did better in CPU . Spikes in CPU contributed to score drop by 29.27%

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

Consider re-merging the code from build v4.0.11, CPU score was 4.1

Build v4.0.11 did better in Network . Spikes in Network contributed to score drop by 10%

6 tests need immediate attention. View performance graph.

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

Build v4.0.11 did better in Memory . Spikes in Memory contributed to score drop by 9.3%

Caching: Use LruCache for data caching to optimize memory usage

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

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

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

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

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

Your average App Dalvik usage surged by 20.79%, Your memory score is 3.9

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

97.54 MB of App Dalvik utilized by activity com.digivive.nexgtv.activities.NumberValidation. View details

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

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

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

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

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

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

Screen Coverage

competition benchmark

This app is ranked #311 in Entertainment