App Quality Dashboard


3.1 / 5

Chhi Score

This app is performing


Medium Risk


Medium Risk




Medium Risk






  • Install time: Icon 5.63 Sec
  • Launch time: Icon 1.35 Sec
  • Application size: Icon 1.29 MB
  • Last tested on : 19/05/2017
  • Build ID
    :   v1.0.1
  • Chhi Score
    :   3.1
  • Change Rate
    :   -6.06 %

What to fix?

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

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

Build v0.0.1 did better in CPU . Spikes in CPU contributed to score drop by 23.08%

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

Build v0.0.1 did better in Network . Spikes in Network contributed to score drop by 8.82%

Build v0.0.1 did better in Memory . Spikes in Memory contributed to score drop by 6.67%

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.

Utilization of CPU is close to the threshold.

Consider re-merging the code from build v0.0.1, CPU score was 2.6

App size increased by 168.75% See how to optimize.

6 tests need immediate attention. View performance graph.

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

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 Oncreate() if the launch time is exceeding more than 3.2 secs. Try deflating views and layouts to optimize.

25.15 MB of App Dalvik utilized by activity View details

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

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

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

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

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.

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.

Your average App Dalvik usage surged by 36.8%, Your memory score is 2.8

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

Screen Coverage

competition benchmark

This app is ranked #1140 in Education