App Quality Dashboard


2.7 / 5

Chhi Score

This app is performing


Medium Risk


Medium Risk




Medium Risk






  • Install time: Icon 24.75 Sec
  • Launch time: Icon 2.76 Sec
  • Application size: Icon 13.89 MB
  • Last tested on : 15/06/2017
  • Build ID
    :   v5.74
  • Chhi Score
    :   2.7
  • Change Rate
    :   +42.11 %

What to fix?

Build v5.73 did better in Memory . Spikes in Memory contributed to score drop by 17.24%

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 2 CPU risks.

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

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

3 tests need immediate attention. View performance graph.

Consider re-merging the code from build v5.73, Memory score was 2.9

Utilization of CPU is close to the threshold.

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

The app's CPU score has improved by 46.67% compared to build v5.73! Good job!

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

Caching: Use LruCache for data caching to optimize memory usage

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

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

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

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

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

38.55 MB of App Dalvik utilized by activity View details

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

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

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

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.

The app's Network score has improved by 14.29% compared to build v5.73! Good job!

Well done, Network consumption has come down by 34.09 % compared to build v5.73

Screen Coverage

competition benchmark

This app is ranked #20 in House & Home