App Quality Dashboard


2.4 / 5

Chhi Score

This app is performing


Medium Risk


Medium Risk


Medium  Risk








  • Install time: Icon 6.24 Sec
  • Launch time: Icon 4.00 Sec
  • Application size: Icon 3.01 MB
  • Last tested on : 28/04/2017
  • Build ID
    :   v2.35
  • Chhi Score
    :   2.4
  • Change Rate
    :   -44.19 %

What to fix?

Build v2.34 did better in Memory . Spikes in Memory contributed to score drop by 39.02%

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

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

Must fix: App crashed because of FATAL EXCEPTION: a Process: com.zyepro.mobilescopes PID: 18096 java.lang.NullPointerException: ... Users with phone manufactured by Karbonn might experience a crash on their phone!. Fix now!

Build v2.34 did better in CPU . Spikes in CPU contributed to score drop by 51.22%

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

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

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 size increased by 46.12% See how to optimize.

Consider re-merging the code from build v2.34, Memory score was 4.1

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

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

Motorola Moto E (2nd gen), Lenovo A6000, Zenfone 2 Laser has moved from Good to Medium risk due to RISK . View details

Utilization of CPU is close to the threshold.

25 tests need immediate attention. View performance graph.

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

Consider re-merging the code from build v2.34, CPU score was 4.1

Utilization of Memory is close to the threshold.

Printing logs on callbacks would make debugging easy for tests run in our platform

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.

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

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

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

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

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

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

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

63.91 MB of App Dalvik utilized by activity com.zyepro.mobilescopes.MainActivity. View details

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.

Caching: Use LruCache for data caching to optimize memory usage

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

Your average App Dalvik usage surged by 22.81%, Your memory score is 2.5

Screen coverage

competition benchmark

This app is ranked #391 in Video Players & Editors