App Quality Dashboard


2.1 / 5

Chhi Score

This app is performing


Medium Risk


High Risk


Medium  Risk








  • Install time: Icon 53.41 Sec
  • Launch time: Icon 4.71 Sec
  • Application size: Icon 31.11 MB
  • Last tested on : 10/10/2017
  • Build ID
    :   v7.13.1
  • Chhi Score
    :   2.1
  • Change Rate
    :   -50 %

What to fix?

Must fix: App crashed because of (17544): [ApplicationCrashHandler]{Thread-30449} - FATAL EXCEPTION!! -- Taking over default han... Users with phone manufactured by Karbonn might experience a crash on their phone!. Fix now!

Potential risk in CPU: Utilization has gone up by 58.54% compared to build v7.9.9

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

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

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

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

10 tests need immediate attention. View performance graph.

Consider re-merging the code from build v7.9.9, CPU score was 4.1

The app took 4.71 seconds to load on Android OS version 6.0. Usually anything more than 3.2 seconds results in user drops. View details

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

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

Build v7.9.9 did better in Memory . Spikes in Memory contributed to score drop by 11.63%

Utilization of CPU is close to the threshold.

Caching: Use LruCache for data caching to optimize memory usage

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

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

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

Your average App Dalvik usage surged by 28.77%, Your memory score is 3.8

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

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!

144 apps having similar CPU load have low Chhi Scores

4 Tests crashed out of 22 Tests. Check where the app crashed. View details

34.34 MB of App Dalvik utilized by activity com.evernote.ui.landing.LandingActivityV7. View details

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

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

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

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

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

Well done, Network consumption has come down by 61.4 % compared to build v7.9.9

The app's Network score has improved by 6.67% compared to build v7.9.9! Good job!

competition benchmark

This app is ranked #921 in Productivity