App Quality Dashboard

Driving directions

1.8 / 5

Chhi Score

This app is performing

Average

Medium Risk

/5

High Risk

/5

Good 

/5

Good

/5

#

 

Category

Rank

  • Install time: Icon 11.73 Sec
  • Launch time: Icon 4.00 Sec
  • Application size: --- 2.64 MB
  • Last tested on : 04/04/2017
  • Build ID
    :   v2.1.1
  • Chhi Score
    :   1.8
  • Change Rate
    :   -40 %

What to fix?

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

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.

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

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

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

Potential risk in CPU: Utilization has gone up by 5.56% compared to build v2.1.0

14 tests need immediate attention. View performance graph.

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

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

Utilization of CPU is close to the threshold.

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

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

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

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

120 apps having similar CPU load have low Chhi Scores

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

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

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!

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

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

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.

39.78 MB of App Dalvik utilized by activity info.zmobile.dev.gpsmapnavigation.MainActivity. View details

Caching: Use LruCache for data caching to optimize memory usage

The app's Network score has improved by 2.5% compared to build v2.1.0! Good job!

competition benchmark

This app is ranked #411 in Maps & Navigation

406
407
408
409
410
back-to-top