App Quality Dashboard

Battery Life Saver

1.4 / 5

Chhi Score

This app is performing

Poor

Medium Risk

/5

Medium Risk

/5

Good 

/5

High Risk

/5

#

 

Category

Rank

  • Install time: Icon 18.27 Sec
  • Launch time: Icon 1.41 Sec
  • Application size: --- 5.60 MB
  • Last tested on : 15/03/2017
  • Build ID
    :   v1.0.3
  • Chhi Score
    :   1.4
  • Change Rate
    :   -57.58 %

What to fix?

5 Risk(s) are due to Data Sent/Received in Network exceeding the threshold.

Fixing Network risks could drastically improve Chhi Score. There are 5 Network risks.

Build v1.0.2 did better in CPU . Spikes in CPU contributed to score drop by 28%

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

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

Build v1.0.2 did better in Memory . Spikes in Memory contributed to score drop by 37.5%

Potential risk in Network: Utilization has gone up by75% compared to build v1.0.2

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

Consider re-merging the code from build v1.0.2, CPU score was 2.5

Consider re-merging the code from build v1.0.2, Network score was 4.8

Consider re-merging the code from build v1.0.2, Memory score was 3.2

11 tests need immediate attention. View performance graph.

Caching: Use LruCache for data caching to optimize memory usage

Network utilization on Motorola Moto E (2nd gen) exceeded 1024 KB, you might want to consider bringing it down

Total Network data consumed was 2034.90KB in Motorola Moto E (2nd gen) , This indicates the app will take 10-15 seconds on 2G network and 8-9 seconds on 3G network to load! View details

Network utilization on Lenovo A6000 exceeded 1024 KB, you might want to consider bringing it down

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

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

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

47.53 MB of App Dalvik utilized by activity com.mesi.batteryextender.MainActivity. View details

Below 10 MB approach would increase app installs in crowded markets such as India, China and Russia!

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.

App makes 2034.90 KB of network requests. Moving this to a background thread will improve load speed. View details

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

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

Fix & Optimize launch time using Flatbuffers for storage and rendering performance.

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

Screen Coverage

competition benchmark

This app is ranked #1752 in Tools

1747
1748
1749
1750
1751
back-to-top