App Quality Dashboard

Keypad Lock Screen

1.6 / 5

Chhi Score

This app is performing

Poor

Medium Risk

/5

Medium Risk

/5

Good 

/5

Medium Risk

/5

#

 

Category

Rank

  • Install time: Icon 5.88 Sec
  • Launch time: Icon 1.65 Sec
  • Application size: Icon 3.35 MB
  • Last tested on : 26/03/2017
  • Build ID
    :   v1.6
  • Chhi Score
    :   1.6
  • Change Rate
    :   -20 %

What to fix?

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

7 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 1.5 did better in Memory . Spikes in Memory contributed to score drop by 22.58%

7 tests need immediate attention. View performance graph.

Consider re-merging the code from build 1.5, Memory score was 3.1

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

Utilization of CPU is close to the threshold.

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

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

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

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

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

58.77 MB of App Dalvik utilized by activity com.m2c.studio.game.rm. View details

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

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

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

Your average App Dalvik usage surged by 33.76%, Your memory score is 2.4

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

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

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

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

Caching: Use LruCache for data caching to optimize memory usage

Well done, Network consumption has come down by 58.69 % compared to build 1.5

The app's Network score has improved by 53.85% compared to build 1.5! Good job!

competition benchmark

This app is ranked #3010 in Lifestyle

3005
3006
3007
3008
3009
back-to-top