App Quality Dashboard


3.8 / 5

Chhi Score

This app is performing


Medium Risk


Medium Risk









  • Install time: Icon 4.87 Sec
  • Launch time: Icon 0.76 Sec
  • Application size: Icon 1.27 MB
  • Last tested on : 29/04/2017
  • Build ID
    :   v3.5.1
  • Chhi Score
    :   3.8
  • Change Rate
    :   -11.63 %

What to fix?

Build v3.5 did better in CPU . Spikes in CPU contributed to score drop by 17.07%

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

Build v3.5 did better in Memory . Spikes in Memory contributed to score drop by 14.63%

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.

1 tests need immediate attention. View performance graph.

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

Consider re-merging the code from build v3.5, CPU score was 4.1

Consider re-merging the code from build v3.5, Memory score was 4.1

Utilization of Memory is close to the threshold.

Caching: Use LruCache for data caching to optimize memory usage

36.80 MB of App Dalvik utilized by activity javalc6.thesaurus.Redirect. View details

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

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

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

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

Your average App Dalvik usage surged by 25.45%, Your memory score is 3.5

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

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

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

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

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.

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

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

Screen coverage

competition benchmark

This app is ranked #538 in Education