App Quality Dashboard


0.5 / 5

Chhi Score

This app is performing


High Risk


High Risk










  • Install time: Icon 27.92 Sec
  • Launch time: Icon 1.15 Sec
  • Application size: Icon 10.00 MB
  • Last tested on : 26/04/2017
  • Build ID
    :   v40.4
  • Chhi Score
    :   0.5
  • Change Rate
    :   -64.29 %

What to fix?

Your App CPU is now in a High Risk Zone. With a small investment into your testing you can improve your app quality better. Get more test coverage

Potential risk in Memory: Utilization has gone up by35% compared to build v40.3

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

Your App Memory is now in a High Risk Zone. With a small investment into your testing you can improve your app quality better. Get more test coverage

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 11 CPU risks.

Potential risk in CPU: Utilization has gone up by 16.67% compared to build v40.3

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

Consider re-merging the code from build v40.3, Memory score was 2.0

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

App size increased by 13.12% See how to optimize.

11 tests need immediate attention. View performance graph.

Caching: Use LruCache for data caching to optimize memory usage

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

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

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

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

213 apps having similar CPU load have low Chhi Scores

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

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.

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

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

44.12 MB of App Dalvik utilized by activity mobi.skyrock.Smax.activity.RegisterActivity. View details

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

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

Well done, Network consumption has come down by 99.12 % compared to build v40.3

The app's Network score has improved by 25% compared to build v40.3! Good job!

Screen Coverage

competition benchmark

This app is ranked #760 in Social