App Quality Dashboard


2.9 / 5

Chhi Score

This app is performing


Medium Risk


Medium Risk


Medium  Risk


Medium Risk






  • Install time: Icon 18.20 Sec
  • Launch time: Icon 0.67 Sec
  • Application size: Icon 18.93 MB
  • Last tested on : 07/04/2017
  • Build ID
    :   v2.0
  • Chhi Score
    :   2.9
  • Change Rate
    :   +81.25 %

What to fix?

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

Must fix: App crashed because of FATAL EXCEPTION: main Process: shirdi.sai.baba PID: 19040 java.lang.IllegalStateException: Can ... Users with phone manufactured by Samsung might experience a crash on their phone!. Fix now!

9 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.

9 tests need immediate attention. View performance graph.

Lava Iris X8, Samsung Duos Galaxy J7, Karbonn Titanium Machfive has moved from Good to Medium risk due to RISK . View details

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

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

App size increased by 87.61% See how to optimize.

The app's Memory score has improved by 25% compared to build v1.0! Good job!

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

44.21 MB of App Dalvik utilized by activity View details

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

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

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

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

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.

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

Caching: Use LruCache for data caching to optimize memory usage

The app has crashed on few device(s)! 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.

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

Screen Coverage

competition benchmark

This app is ranked #1174 in Entertainment