App Quality Dashboard


1.9 / 5

Chhi Score

This app is performing


Medium Risk


High Risk










  • Install time: Icon 32.63 Sec
  • Launch time: Icon 2.05 Sec
  • Application size: Icon 12.81 MB
  • Last tested on : 23/03/2017
  • Build ID
    :   v4.5.0
  • Chhi Score
    :   1.9
  • Change Rate
    :   -50 %

What to fix?

Fixing CPU risks could drastically improve Chhi Score. There are 16 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.

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

Build 4.4.0 did better in Memory . Spikes in Memory contributed to score drop by 16.67%

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

Potential risk in CPU: Utilization has gone up by 37.5% compared to build 4.4.0

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

Consider re-merging the code from build 4.4.0, CPU score was 2.4

Consider re-merging the code from build 4.4.0, Memory score was 3.6

Build 4.4.0 did better in Network . Spikes in Network contributed to score drop by 4.35%

16 tests need immediate attention. View performance graph.

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.

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

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

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

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

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!

Your average App Dalvik usage surged by 2.56%, Your memory score is 3.0

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.

121.01 MB of App Dalvik utilized by activity com.commonfloor.CfcityLanding. View details

Caching: Use LruCache for data caching to optimize memory usage

574 apps having similar CPU load have low Chhi Scores

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

Screen Coverage

competition benchmark

This app is ranked #2659 in Lifestyle