App Quality Dashboard


2.0 / 5

Chhi Score

This app is performing


Medium Risk


Medium Risk


Medium  Risk








  • Install time: Icon 26.69 Sec
  • Launch time: Icon 0.73 Sec
  • Application size: Icon 25.35 MB
  • Last tested on : 03/05/2017
  • Build ID
    :   v3.3.1.14
  • Chhi Score
    :   2.0
  • Change Rate
    :   +233.33 %

What to fix?

Must fix: App crashed because of 9301): *** FATAL EXCEPTION IN SYSTEM PROCESS: main 9301): java.lang.NullPointerException: Atte... Users with phone manufactured by LYF might experience a crash on their phone!. Fix now!

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

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

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.

Utilization of CPU is close to the threshold.

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

The app's CPU score has improved by 130% compared to build v3.2.1.14! Good job!

The app's Memory score has improved by 31.25% compared to build v3.2.1.14! Good job!

Motorola Moto E (2nd gen), Panasonic P55, Lenovo VIBE K4 Note has moved from Good to Medium risk due to RISK . View details

14 tests need immediate attention. View performance graph.

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

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

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

66.71 MB of App Dalvik utilized by activity View details

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

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

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

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

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

Caching: Use LruCache for data caching to optimize memory usage

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

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

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

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

Well done, Network consumption has come down by 99.73 % compared to build v3.2.1.14

The app's Network score has improved by 108.33% compared to build v3.2.1.14! Good job!

Screen Coverage

competition benchmark

This app is ranked #929 in Productivity