App Quality Dashboard

Ultimate Driving Mode

0.3 / 5

Chhi Score

This app is performing

Poor

High Risk

/5

High Risk

/5

Good 

/5

Good

/5

#

 

Category

Rank

  • Install time: Icon 41.00 Sec
  • Launch time: Icon 19.83 Sec
  • Application size: Icon 40.43 MB
  • Last tested on : 04/05/2017
  • Build ID
    :   v1.7
  • Chhi Score
    :   0.3
  • Change Rate
    :   0%

What to fix?

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

Potential risk in CPU: Utilization has gone up by 5.88% compared to build v1.6.4

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

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

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

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.

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

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

20 tests need immediate attention. View performance graph.

Make sure your App's PSS isn't too high. Freeing objects that aren't needed would reduce chances of getting unexpectedly killed by Android system.

The app took 19.83 seconds to load on Android OS version 5.0.2. Usually anything more than 3.2 seconds results in user drops. View details

Build v1.6.4 did better in Network . Spikes in Network contributed to score drop by 2.04%

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

Utilization of CPU is close to the threshold.

The app's memory score is 0.5 due to high memory utilization. Needs to be fixed as priority.

20 Risk(s) are due to App Total in Memory exceeding the threshold.

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

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

Caching: Use LruCache for data caching to optimize memory usage

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

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

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

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

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.

69.63 MB of App Dalvik utilized by activity com.customsolutions.android.udm.AssistantPermissions. View details

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

22 apps having similar CPU load have low Chhi Scores

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

Screen coverage

competition benchmark

This app is ranked #119 in Auto & Vehicles

114
115
116
117
118
back-to-top