App Quality Dashboard

ZAP

3.7 / 5

Chhi Score

This app is performing

Average

Medium Risk

/5

Medium Risk

/5

Good 

/5

Good

/5

#

 

Category

Rank

  • Install time: Icon 12.63 Sec
  • Launch time: Icon 0.83 Sec
  • Application size: Icon 4.14 MB
  • Last tested on : 12/04/2017
  • Build ID
    :   v1.1
  • Chhi Score
    :   3.7
  • Change Rate
    :   -2.63 %

What to fix?

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

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

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

Build v1.0.0 did better in CPU . Spikes in CPU contributed to score drop by 12.9%

Utilization of CPU is close to the threshold.

6 tests need immediate attention. View performance graph.

Build v1.0.0 did better in Memory . Spikes in Memory contributed to score drop by 2.7%

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

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

Caching: Use LruCache for data caching to optimize memory usage

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

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.

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

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

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

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

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.

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

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

Your average App Dalvik usage surged by 35.88%, Your memory score is 3.6

41.27 MB of App Dalvik utilized by activity com.zoomcar.zapflexi.activities.ZoomAuthActivity. View details

The app's Network score has improved by 2.27% compared to build v1.0.0! Good job!

Well done, Network consumption has come down by 15.91 % compared to build v1.0.0

competition benchmark

This app is ranked #314 in Travel & Local

309
310
311
312
313
back-to-top