App Quality Dashboard

AppLock Pro

2.3 / 5

Chhi Score

This app is performing

Average

Memory

Medium Risk

/5

CPU

High Risk

/5

crash

Good 

/5

network

Good

/5

Competition

#

 

Category

Rank

  • Install time: Icon 17.92 Sec
  • Launch time: Icon 0.56 Sec
  • Application size: Icon 8.74 MB
  • Last tested on : 07/05/2017
  • Build ID
    :   vv1.66
  • Chhi Score
    :   2.3
  • Change Rate
    :   +91.67 %

Insights (24)

What to fix?

12 Risk(s) are due to Threads in CPU exceeding the threshold.
Fixing CPU risks could drastically improve Chhi Score. There are 12 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.
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
App launch time went up by INF% initlizate network calls after few seconds of loading the resources. View details
Build vv1.64.3 did better in Memory . Spikes in Memory contributed to score drop by 5%
12 tests need immediate attention. View performance graph.
The app has a high performance risk for the phone manufacturer(s) Lenovo, YU, Asus, Lava, Panasonic, LYF, Karbonn. Check coverage report for more details.
47.10 MB of App Dalvik utilized by activity com.jiubang.alock.ui.activities.NewGuideActivity. View details
Upload APKs with and without 3rd Party SDKs to monitor and optimize the impact of app performance
Printing logs on callbacks would make debugging easy for tests run in our platform
Fix & Optimize launch time using Flatbuffers for storage and rendering performance.
Below 10 MB approach would increase app installs in crowded markets such as India, China and Russia!
Caching: Use LruCache for data caching to optimize memory usage
Optimize the app to render elements at 60 FPS for buttery smooth experience.
There is high probability of identifying risks running the apps with conditions
Do not initialize objects that aren't necessary during launch times. Moving to singleton pattern helps
Your average App Dalvik usage surged by 43.68%, Your memory score is 3.8
Fix Oncreate() if the launch time is exceeding more than 3.2 secs. Try deflating views and layouts to optimize.
Follow simple UI hierarchy by reducing nested layouts to Relative layouts.
Testability: Providing login / sign-up details could very well improve depth of bot clicks
Avoid wake-locks in background, using Batch and schedulers APIs such as GCM, Job schedulers could reduce wake-locks
Coverage: Android version coverage for reports will range between 5.1.1 to 7.1.2
347 apps having similar CPU load have low Chhi Scores
Unlock more fixes

Screen Coverage

competition benchmark

This app is ranked #1500 in Tools

1495
1496
1497
1498
1499
back-to-top