App Quality Dashboard

Battery Life

2.8 / 5

Chhi Score

This app is performing

Average

Memory

Medium Risk

/5

CPU

Medium Risk

/5

crash

Good 

/5

network

Medium Risk

/5

Competition

#

 

Category

Rank

  • Install time: Icon 12.67 Sec
  • Launch time: Icon 4.76 Sec
  • Application size: Icon 2.44 MB
  • Last tested on : 05/03/2017
  • Build ID
    :   v1.1.6
  • Chhi Score
    :   2.8
  • Change Rate
    :   -34.88 %

Insights (29)

What to fix?

Fixing CPU risks could drastically improve Chhi Score. There are 6 CPU risks.
6 Risk(s) are due to Threads in CPU exceeding the threshold.
7 Risk(s) are due to App PSS in Memory exceeding the threshold. See how to optimize memory and remove 7 High Risk(s).
Build v1.1.5 did better in Memory . Spikes in Memory contributed to score drop by 36.59%
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.
Build v1.1.5 did better in CPU . Spikes in CPU contributed to score drop by 51.22%
Consider re-merging the code from build v1.1.5, Memory score was 4.1
Utilization of CPU is close to the threshold.
The app took 4.76 seconds to load on Android OS version 5.0.2. Usually anything more than 3.2 seconds results in user drops. View details
Make sure your App's PSS isn't too high. Freeing objects that aren't needed would reduce chances of getting unexpectedly killed by Android system.
9 tests need immediate attention. View performance graph.
Utilization of Memory is close to the threshold.
The app has a high performance risk for the phone manufacturer(s) Motorola, Karbonn, Lenovo, YU, Micromax, Asus. Check coverage report for more details.
Consider re-merging the code from build v1.1.5, CPU score was 4.1
Testability: Providing login / sign-up details could very well improve depth of bot clicks
Coverage: Android version coverage for reports will range between 5.1.1 to 7.1.2
Follow simple UI hierarchy by reducing nested layouts to Relative layouts.
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
Optimize the app to render elements at 60 FPS for buttery smooth experience.
Printing logs on callbacks would make debugging easy for tests run in our platform
Fix & Optimize launch time using Flatbuffers for storage and rendering performance.
Avoid wake-locks in background, using Batch and schedulers APIs such as GCM, Job schedulers could reduce wake-locks
41.79 MB of App Dalvik utilized by activity kr.co.core_technology.batterylife.MainActivity. View details
Fix Oncreate() if the launch time is exceeding more than 3.2 secs. Try deflating views and layouts to optimize.
Your average App Dalvik usage surged by 6.64%, Your memory score is 2.6
There is high probability of identifying risks running the apps with conditions
Do not initialize objects that aren't necessary during launch times. Moving to singleton pattern helps
Caching: Use LruCache for data caching to optimize memory usage
Unlock more fixes

Screen coverage

competition benchmark

This app is ranked #1362 in Tools

1357
1358
1359
1360
1361
back-to-top