App Quality Dashboard


2.5 / 5

Chhi Score

This app is performing


Medium Risk


Medium Risk










  • Install time: Icon 28.92 Sec
  • Launch time: Icon 0.72 Sec
  • Application size: Icon 34.63 MB
  • Last tested on : 31/03/2017
  • Build ID
    :   v5.0
  • Chhi Score
    :   2.5
  • Change Rate
    :   -24.24 %

What to fix?

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

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

Build v3.0 did better in Memory . Spikes in Memory contributed to score drop by 31.25%

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.

Build v3.0 did better in CPU . Spikes in CPU contributed to score drop by 25.93%

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

Utilization of CPU is close to the threshold.

Consider re-merging the code from build v3.0, CPU score was 2.7

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

11 tests need immediate attention. View performance graph.

Consider re-merging the code from build v3.0, Memory score was 3.2

App size increased by 251.57% See how to optimize.

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

Caching: Use LruCache for data caching to optimize memory usage

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

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

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

Your average App Dalvik usage surged by 41.74%, Your memory score is 2.2

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

66.63 MB of App Dalvik utilized by activity com.zeemish.spanish.quick.BasicsActivity. View details

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

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

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

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

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

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

Well done, Network consumption has come down by 45.3 % compared to build v3.0

Screen Coverage

competition benchmark

This app is ranked #1623 in Education