App Quality Dashboard

99

0.7 / 5

Chhi Score

This app is performing

Poor

Medium Risk

/5

High Risk

/5

Good 

/5

Good

/5

#

 

Category

Rank

  • Install time: Icon 17.76 Sec
  • Launch time: Icon 2.48 Sec
  • Application size: Icon 7.95 MB
  • Last tested on : 03/05/2017
  • Build ID
    :   v4.18.2
  • Chhi Score
    :   0.7
  • Change Rate
    :   +16.67 %

What to fix?

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.

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

Fixing CPU risks could drastically improve Chhi Score. There are 20 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

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

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

20 tests need immediate attention. View performance graph.

The app's Memory score has improved by 23.53% compared to build v4.17.3! Good job!

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

120 apps having similar CPU load have low Chhi Scores

48.70 MB of App Dalvik utilized by activity com.taxis99.v2.view.activity.PickUpActivity. View details

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.

Caching: Use LruCache for data caching to optimize memory usage

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

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

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

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

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.

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

Well done, Network consumption has come down by 28.84 % compared to build v4.17.3

Screen Coverage

competition benchmark

This app is ranked #490 in Maps & Navigation

485
486
487
488
489
back-to-top