App Quality Dashboard

Apowersoft Screen Recorder

3.1 / 5

Chhi Score

This app is performing

Average

Memory

Medium Risk

/5

CPU

Medium Risk

/5

crash

Good 

/5

network

Good

/5

Competition

#

 

Category

Rank

  • Install time: Icon 9.50 Sec
  • Launch time: Icon 4.00 Sec
  • Application size: Icon 5.25 MB
  • Last tested on : 27/04/2017
  • Build ID
    :   v1.2.4
  • Chhi Score
    :   3.1
  • Change Rate
    :   0%

Insights (23)

What to fix?

Build v1.2.0 did better in Memory . Spikes in Memory contributed to score drop by 3.23%
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.
7 tests need immediate attention. View performance graph.
The app's CPU score has improved by 6.25% compared to build v1.2.0! Good job!
Utilization of CPU is close to the threshold.
The app has a high performance risk for the phone manufacturer(s) Lenovo, Motorola, Asus. Check coverage report for more details.
The app took 4.00 seconds to load on Android OS version 5.0.2. Usually anything more than 3.2 seconds results in user drops. View details
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!
Caching: Use LruCache for data caching to optimize memory usage
Fix Oncreate() if the launch time is exceeding more than 3.2 secs. Try deflating views and layouts to optimize.
72.38 MB of App Dalvik utilized by activity com.apowersoft.screenrecord.activity.VideoActivity. View details
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
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
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
Avoid wake-locks in background, using Batch and schedulers APIs such as GCM, Job schedulers could reduce wake-locks
Fix & Optimize launch time using Flatbuffers for storage and rendering performance.
Do not initialize objects that aren't necessary during launch times. Moving to singleton pattern helps
The app's Network score has improved by 2.04% compared to build v1.2.0! Good job!
Well done, Network consumption has come down by 86.44 % compared to build v1.2.0
Unlock more fixes
competition benchmark

This app is ranked #741 in Productivity

736
737
738
739
740
back-to-top