App Quality Dashboard


3.4 / 5

Chhi Score

This app is performing


Medium Risk


Medium Risk










  • Install time: Icon 18.00 Sec
  • Launch time: Icon 2.04 Sec
  • Application size: Icon 7.05 MB
  • Last tested on : 27/04/2017
  • Build ID
    :   v1.53
  • Chhi Score
    :   3.4
  • Change Rate
    :   -17.07 %

What to fix?

Build v1.41 did better in CPU . Spikes in CPU contributed to score drop by 17.07%

Build v1.41 did better in Memory . Spikes in Memory contributed to score drop by 17.07%

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.

1 tests need immediate attention. View performance graph.

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

Consider re-merging the code from build v1.41, CPU score was 4.1

Consider re-merging the code from build v1.41, Memory score was 4.1

Utilization of CPU is close to the threshold.

Your average App Dalvik usage surged by 38.77%, Your memory score is 3.4

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

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

41.03 MB of App Dalvik utilized by activity chat.anti.activities.RegOne. View details

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

Caching: Use LruCache for data caching to optimize memory usage

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

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

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

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

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

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

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

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

Screen Coverage

competition benchmark

This app is ranked #27 in Dating