App Quality Dashboard


0.2 / 5

Chhi Score

This app is performing


High Risk


Medium Risk


Medium  Risk








  • Install time: Icon 7.76 Sec
  • Launch time: Icon 1.72 Sec
  • Application size: --- 5.65 MB
  • Last tested on : 24/05/2017
  • Build ID
    :   v120
  • Chhi Score
    :   0.2
  • Change Rate
    :   -33.33 %

What to fix?

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

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

Your App Memory 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

2 Risk(s) are due to App Dalvik in Memory exceeding the threshold. See how to optimize memory and remove 2 High Risk(s).

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.

Motorola Moto G 2014 XT1068 Dual 8GB, Motorola Moto E (2nd gen), Motorola Nexus 6 has moved from Good to High risk due to CRASH . View details

Must fix: App crashed because of FATAL EXCEPTION: main Process: com.guides.minube.lisboa PID: 15337 android.database.sqlite.SQLi... Users with phone manufactured by Motorola might experience a crash on their phone!. Fix now!

2 Risk(s) are due to App Dalvik in Memory exceeding the threshold.

The app's memory score is 0.5 due to high memory utilization. Needs to be fixed as priority.

20 tests need immediate attention. View performance graph.

Utilization of CPU is close to the threshold.

The app's CPU score has improved by 3.7% compared to build v4.0! Good job!

The app has a high performance risk for the phone manufacturer(s) Panasonic, Karbonn, YU, Spice, OnePlus, Motorola. Check coverage report for more details.

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

3 Tests crashed out of 21 Tests. Check where the app crashed. View details

Caching: Use LruCache for data caching to optimize memory usage

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

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

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

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

83.00 MB of App Dalvik utilized by activity 14054. View details

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

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

The app has crashed on few device(s)! View details

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

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

The app's Network score has improved by 2.17% compared to build v4.0! Good job!

Well done, Network consumption has come down by 30.52 % compared to build v4.0

Screen Coverage

competition benchmark

This app is ranked #1170 in Travel & Local