App Quality Dashboard

Car Info

2.1 / 5

Chhi Score

This app is performing

Average

Medium Risk

/5

High Risk

/5

Good 

/5

Medium Risk

/5

#

 

Category

Rank

  • Install time: Icon 7.57 Sec
  • Launch time: Icon 1.26 Sec
  • Application size: Icon 3.38 MB
  • Last tested on : 04/05/2017
  • Build ID
    :   v2.1.2
  • Chhi Score
    :   2.1
  • Change Rate
    :   +31.25 %

What to fix?

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

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

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

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.

The app's CPU score has improved by 8.33%

7 tests need immediate attention. View performance graph.

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

Build v2.1.1 did better in Network . Spikes in Network contributed to score drop by 4.76%

The app's Memory score has improved by 37.5% compared to build v2.1.1! Good job!

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

120 apps having similar CPU load have low Chhi Scores

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

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

26.56 MB of App Dalvik utilized by activity com.cuvora.carinfo.SearchActivity. View details

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

Caching: Use LruCache for data caching to optimize memory usage

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

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.

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

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

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

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

Screen Coverage

competition benchmark

This app is ranked #394 in Maps & Navigation

389
390
391
392
393
back-to-top