App Quality Dashboard


2.2 / 5

Chhi Score

This app is performing


Medium Risk


High Risk


Medium  Risk


Medium Risk






  • Install time: Icon 39.38 Sec
  • Launch time: Icon 13.42 Sec
  • Application size: Icon 13.61 MB
  • Last tested on : 10/10/2017
  • Build ID
    :   v6.36.0
  • Chhi Score
    :   2.2
  • Change Rate
    :   -43.59 %

Testing depth





Depth Details

What to fix?

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

Must fix: App crashed because of 961): java.lang.RuntimeException: here 961): at Users with phone manufactured by LYF might experience a crash on their phone!. Fix now!

12 Risk(s) are due to Threads in CPU 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 15 CPU risks.

Potential risk in CPU: Utilization has gone up by 38.1% compared to build v6.10.0

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

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

Build v6.10.0 did better in Memory . Spikes in Memory contributed to score drop by 5%

11 Risk(s) are due to CPU Load in CPU exceeding the threshold.

Samsung Duos Galaxy J7, YU Yuphoria, Samsung Duos Galaxy J7 has moved from Good to Medium risk due to RISK . View details

14 tests need immediate attention. View performance graph.

The app took 13.42 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 v6.10.0, CPU score was 2.1

Utilization of CPU is close to the threshold.

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

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

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

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

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

213 apps having similar CPU load have low Chhi Scores

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

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

42.34 MB of App Dalvik utilized by activity com.pinterest.activity.unauth.UnauthActivity. View details

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

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

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

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

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

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

Screen coverage

competition benchmark

This app is ranked #600 in Social