App Quality Dashboard

 Flashlight

0.6 / 5

Chhi Score

This app is performing

Poor

Medium Risk

/5

High Risk

/5

Medium  Risk

/5

Medium Risk

/5

#

 

Category

Rank

  • Install time: Icon 17.67 Sec
  • Launch time: Icon 2.30 Sec
  • Application size: Icon 6.87 MB
  • Last tested on : 10/10/2017
  • Build ID
    :   v1.1.8
  • Chhi Score
    :   0.6
  • Change Rate
    :   -40 %

What to fix?

3 Risk(s) are due to Data Sent/Received in Network 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.

Build 1.1.4 did better in Memory . Spikes in Memory contributed to score drop by 36.67%

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

Must fix: App crashed because of 958): java.lang.RuntimeException: here 958): at com.android.server.am.ActivityManagerService... Users with phone manufactured by Panasonic might experience a crash on their phone!. Fix now!

Must fix: App crashed because of 958): java.lang.RuntimeException: here 958): at com.android.server.am.ActivityManagerService... Users with phone manufactured by Karbonn might experience a crash on their phone!. Fix now!

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

Must fix: App crashed because of 958): java.lang.RuntimeException: here 958): at com.android.server.am.ActivityManagerService... Users with phone manufactured by LYF might experience a crash on their phone!. Fix now!

Build 1.1.4 did better in Network . Spikes in Network contributed to score drop by 22.73%

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

Must fix: App crashed because of 958): java.lang.RuntimeException: here 958): at com.android.server.am.ActivityManagerService... Users with phone manufactured by InFocus might experience a crash on their phone!. Fix now!

Consider re-merging the code from build 1.1.4, Memory score was 3.0

29 tests need immediate attention. View performance graph.

Consider re-merging the code from build 1.1.4, Network score was 4.4

14 Risk(s) are due to CPU Load in CPU exceeding the threshold.

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

App size increased by 36.04% See how to optimize.

Lenovo A6000, Spice Mi-498 Dream Uno, Panasonic P55 has moved from Good to Medium risk due to RISK . View details

Utilization of CPU is close to the threshold.

The app's memory score is 1.9 due to high memory utilization. Needs to be fixed as priority.

The app has crashed on few device(s)! View details

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

41.35 MB of App Dalvik utilized by activity com.surpax.ledflashlight.FlashlightActivity. View details

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

Total Network data consumed was 1319.07KB in Lenovo A6000 , This indicates the app will take 10-15 seconds on 2G network and 8-9 seconds on 3G network to load! View details

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

144 apps having similar CPU load have low Chhi Scores

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

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

Caching: Use LruCache for data caching to optimize memory usage

Your average App Dalvik usage surged by 11.7%, Your memory score is 1.9

Network utilization on Micromax Canvas A1 AQ4502 exceeded 1024 KB, you might want to consider bringing it down

4 Tests crashed out of 33 Tests. Check where the app crashed. View details

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

Coverage: Android version coverage for reports will range between 5.1.1 to 7.1.2

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

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

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

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

Screen Coverage

competition benchmark

This app is ranked #1076 in Productivity

1071
1072
1073
1074
1075
back-to-top