App Quality Dashboard


4.0 / 5

Chhi Score

This app is performing


Medium Risk


Medium Risk




Medium Risk






  • Install time: Icon 18.24 Sec
  • Launch time: Icon 3.61 Sec
  • Application size: Icon 10.97 MB
  • Last tested on : 25/04/2017
  • Build ID
    :   v3036
  • Chhi Score
    :   4.0
  • Change Rate
    :   +8.11 %

What to fix?

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.

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

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

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

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

27 tests need immediate attention. View performance graph.

Utilization of CPU is close to the threshold.

The app took 3.61 seconds to load on Android OS version 5.0.2. Usually anything more than 3.2 seconds results in user drops. View details

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

50.25 MB of App Dalvik utilized by activity com.mobilityflow.torrent.MainView. View details

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

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

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

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.

Caching: Use LruCache for data caching to optimize memory usage

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

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

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

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

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

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

Well done, Network consumption has come down by 18.22 % compared to build v3035

Screen Coverage

competition benchmark

This app is ranked #122 in Video Players & Editors