App Quality Dashboard

Штрафы ПДД

3.5 / 5

Chhi Score

This app is performing


Medium Risk


Medium Risk










  • Install time: Icon 16.80 Sec
  • Launch time: Icon 0.79 Sec
  • Application size: --- 16.59 MB
  • Last tested on : 23/04/2017
  • Build ID
    :   v5.9.8
  • Chhi Score
    :   3.5
  • Change Rate
    :   +6.06 %

What to fix?

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

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

Build v1.0.3 did better in Memory . Spikes in Memory contributed to score drop by 21.95%

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

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 v1.0.3 did better in CPU . Spikes in CPU contributed to score drop by 56.1%

Consider re-merging the code from build v1.0.3, CPU score was 4.1

Consider re-merging the code from build v1.0.3, Memory score was 4.1

App size increased by 2862.5% See how to optimize.

Build v1.0.3 did better in Network . Spikes in Network contributed to score drop by 8.16%

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

9 tests need immediate attention. View performance graph.

Utilization of CPU is close to the threshold.

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

Caching: Use LruCache for data caching to optimize memory usage

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

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.

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

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

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

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

43.51 MB of App Dalvik utilized by activity View details

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

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

Your average App Dalvik usage surged by 26.25%, Your memory score is 3.2

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

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

Screen Coverage

competition benchmark

This app is ranked #41 in Auto & Vehicles