App Quality Dashboard

QuickCollage

0.9 / 5

Chhi Score

This app is performing

Poor

Medium Risk

/5

High Risk

/5

Good 

/5

Medium Risk

/5

#

 

Category

Rank

  • Install time: Icon 22.33 Sec
  • Launch time: Icon 0.55 Sec
  • Application size: --- 20.03 MB
  • Last tested on : 26/04/2017
  • Build ID
    :   v1.20
  • Chhi Score
    :   0.9
  • Change Rate
    :   0%

What to fix?

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

Build v1.19 did better in Memory . Spikes in Memory contributed to score drop by 3.57%

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

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

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

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

Utilization of Memory is close to the threshold.

9 tests need immediate attention. View performance graph.

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

Build v1.19 did better in Network . Spikes in Network contributed to score drop by 7.14%

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

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.

Caching: Use LruCache for data caching to optimize memory usage

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

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

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

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

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.

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

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

64.03 MB of App Dalvik utilized by activity com.google.android.gms.ads.AdActivity. View details

358 apps having similar CPU load have low Chhi Scores

Screen coverage

competition benchmark

This app is ranked #1005 in Photography

1000
1001
1002
1003
1004
back-to-top