App Quality Dashboard

Pickup Lines

1.5 / 5

Chhi Score

This app is performing


Medium Risk


High Risk




High Risk






  • Install time: Icon 8.78 Sec
  • Launch time: Icon 3.25 Sec
  • Application size: Icon 3.63 MB
  • Last tested on : 18/05/2017
  • Build ID
    :   v2.02
  • Chhi Score
    :   1.5
  • Change Rate
    :   -6.25 %

What to fix?

Potential risk in CPU: Utilization has gone up by 26.67% compared to build v2.01

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

Potential risk in Network: Utilization has gone up by70% compared to build v2.01

Build v2.01 did better in Memory . Spikes in Memory contributed to score drop by 17.39%

Fixing Network risks could drastically improve Chhi Score. There are 27 Network risks.

27 Risk(s) are due to Data Sent/Received in Network 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.

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

23 Risk(s) are due to App PSS in Memory exceeding the threshold. See how to optimize memory and remove 23 High Risk(s).

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

Make sure your App's PSS isn't too high. Freeing objects that aren't needed would reduce chances of getting unexpectedly killed by Android system.

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

Utilization of Memory is close to the threshold.

27 tests need immediate attention. View performance graph.

Utilization of CPU is close to the threshold.

8 Risk(s) are due to App Total in Memory exceeding the threshold.

Consider re-merging the code from build v2.01, Network score was 4.0

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

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

Caching: Use LruCache for data caching to optimize memory usage

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

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

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

508 apps having similar CPU load have low Chhi Scores

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

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

102.25 MB of App Dalvik utilized by activity com.cliqs.pickuplines.activity.CategoryListActivity. View details

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

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

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

Network utilization on Lenovo A6000 exceeded 1024 KB, you might want to consider bringing it down

Total Network data consumed was 3343.20KB in Lenovo A6000 , This indicates the app will take 10-15 seconds on 2G network and 8-9 seconds on 3G network to load! View details

Network utilization on Zenfone 2 Laser exceeded 1024 KB, you might want to consider bringing it down

App makes 3343.20 KB of network requests. Moving this to a background thread will improve load speed. View details

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

Screen coverage

competition benchmark

This app is ranked #2072 in Entertainment