App Quality Dashboard

clever-tanken

3.4 / 5

Chhi Score

This app is performing

Average

Memory

Medium Risk

/5

CPU

Medium Risk

/5

crash

Good 

/5

network

Good

/5

Competition

#

 

Category

Rank

  • Install time: Icon 16.88 Sec
  • Launch time: Icon 1.72 Sec
  • Application size: --- 9.37 MB
  • Last tested on : 22/03/2017
  • Build ID
    :   v5.1.1
  • Chhi Score
    :   3.4
  • Change Rate
    :   +70 %

Insights (24)

What to fix?

Fixing CPU risks could drastically improve Chhi Score. There are 13 CPU risks.
Build v5.1.0 did better in Memory . Spikes in Memory contributed to score drop by 3.13%
13 Risk(s) are due to Threads in CPU exceeding the threshold.
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 has a high performance risk for the phone manufacturer(s) Samsung, Lenovo, Karbonn, YU, Panasonic, LYF, Asus. Check coverage report for more details.
13 tests need immediate attention. View performance graph.
The app's CPU score has improved by 11.11% compared to build v5.1.0! Good job!
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
Caching: Use LruCache for data caching to optimize memory usage
Fix Oncreate() if the launch time is exceeding more than 3.2 secs. Try deflating views and layouts to optimize.
There is high probability of identifying risks running the apps with conditions
Follow simple UI hierarchy by reducing nested layouts to Relative layouts.
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
Optimize the app to render elements at 60 FPS for buttery smooth experience.
56.25 MB of App Dalvik utilized by activity de.mobilesoftwareag.clevertanken.CleverTankenActivity. View details
Fix & Optimize launch time using Flatbuffers for storage and rendering performance.
Coverage: Android version coverage for reports will range between 5.1.1 to 7.1.2
Printing logs on callbacks would make debugging easy for tests run in our platform
Avoid wake-locks in background, using Batch and schedulers APIs such as GCM, Job schedulers could reduce wake-locks
Your average App Dalvik usage surged by 4.15%, Your memory score is 3.1
Well done, Network consumption has come down by 24.04 % compared to build v5.1.0
The app's Network score has improved by 4.76% compared to build v5.1.0! Good job!
Unlock more fixes

Screen Coverage

competition benchmark

This app is ranked #448 in Travel & Local

443
444
445
446
447
back-to-top