App Quality Dashboard

Lock Screen

2.5 / 5

Chhi Score

This app is performing


Medium Risk


Medium Risk










  • Install time: Icon 10.26 Sec
  • Launch time: Icon 3.53 Sec
  • Application size: Icon 2.65 MB
  • Last tested on : 02/04/2017
  • Build ID
    :   v1.2
  • Chhi Score
    :   2.5
  • Change Rate
    :   -40.48 %

What to fix?

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

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

Fixing CPU risks could drastically improve Chhi Score. There are 17 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.1.3 did better in Memory . Spikes in Memory contributed to score drop by 48.84%

Build v1.1.3 did better in CPU . Spikes in CPU contributed to score drop by 53.66%

Utilization of CPU is close to the threshold.

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

Consider re-merging the code from build v1.1.3, CPU score was 4.1

19 tests need immediate attention. View performance graph.

Consider re-merging the code from build v1.1.3, Memory score was 4.3

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

71.88 MB of App Dalvik utilized by activity com.bsoft.keypadlockscreenseries.activity.SetPasswordActivity. View details

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

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

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

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

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 50.87%, Your memory score is 2.2

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

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

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

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

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

Screen Coverage

competition benchmark

This app is ranked #2190 in Lifestyle