App Quality Dashboard

Flower Lock Screen

3.6 / 5

Chhi Score

This app is performing


Medium Risk


Medium Risk




Medium Risk






  • Install time: Icon 10.38 Sec
  • Launch time: Icon 0.26 Sec
  • Application size: Icon 10.34 MB
  • Last tested on : 01/05/2017
  • Build ID
    :   v1.1
  • Chhi Score
    :   3.6
  • Change Rate
    :   -7.69 %

What to fix?

12 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.

Build v1.0 did better in Memory . Spikes in Memory contributed to score drop by 5.56%

Build v1.0 did better in CPU . Spikes in CPU contributed to score drop by 5%

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

Utilization of CPU is close to the threshold.

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

12 tests need immediate attention. View performance graph.

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

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

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

94.89 MB of App Dalvik utilized by activity com.ccloud.flowersphotolockscreen.MainActivity. View details

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

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

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.

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

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

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

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

Your average App Dalvik usage surged by 38.3%, Your memory score is 3.4

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

The app's Network score has improved by 81.82% compared to build v1.0! Good job!

Well done, Network consumption has come down by 67.35 % compared to build v1.0

Screen Coverage

competition benchmark

This app is ranked #834 in Lifestyle