App Quality Dashboard

MP4Cutter

1.9 / 5

Chhi Score

This app is performing

Average

Medium Risk

/5

High Risk

/5

Good 

/5

Medium Risk

/5

#

 

Category

Rank

  • Install time: Icon 12.94 Sec
  • Launch time: Icon 3.44 Sec
  • Application size: Icon 3.36 MB
  • Last tested on : 05/03/2017
  • Build ID
    :   v1.7.1
  • Chhi Score
    :   1.9
  • Change Rate
    :   -36.67 %

What to fix?

Potential risk in CPU: Utilization has gone up by 5.56% compared to build 1.7

3 Risk(s) are due to Data Sent/Received in Network 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.

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

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

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

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

Build 1.7 did better in Network . Spikes in Network contributed to score drop by 23.33%

The app's Memory score has improved by 7.41% compared to build 1.7! Good job!

Consider re-merging the code from build 1.7, Network score was 3.0

Utilization of CPU is close to the threshold.

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

18 tests need immediate attention. View performance graph.

Caching: Use LruCache for data caching to optimize memory usage

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

140 apps having similar CPU load have low Chhi Scores

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

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

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

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

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

41.89 MB of App Dalvik utilized by activity com.beka.tools.mp4cutter.MainActivity. View details

Total Network data consumed was 3377.84KB in Lenovo A6000 , This indicates the app will take 10-15 seconds on 2G network and 8-9 seconds on 3G network to load! View details

Network utilization on Lenovo A6000 exceeded 1024 KB, you might want to consider bringing it down

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

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

App makes 3377.84 KB of network requests. Moving this to a background thread will improve load speed. View details

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

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

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

Screen Coverage

competition benchmark

This app is ranked #470 in Video Players & Editors

465
466
467
468
469
back-to-top