App Quality Dashboard

Rose Gold Diamond Theme

2.9 / 5

Chhi Score

This app is performing

Average

Memory

Medium Risk

/5

CPU

Medium Risk

/5

crash

Good 

/5

network

Good

/5

Competition

#

 

Category

Rank

  • Install time: Icon 6.23 Sec
  • Launch time: Icon 0.24 Sec
  • Application size: Icon 3.55 MB
  • Last tested on : 29/03/2017
  • Build ID
    :   v1.1.3
  • Chhi Score
    :   2.9
  • Change Rate
    :   -12.12 %

Insights (27)

What to fix?

6 Risk(s) are due to Threads in CPU exceeding the threshold.
Build v1.1.1 did better in CPU . Spikes in CPU contributed to score drop by 32.35%
Build v1.1.1 did better in Memory . Spikes in Memory contributed to score drop by 15.63%
Fixing CPU risks could drastically improve Chhi Score. There are 6 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.
App size increased by 43.72% See how to optimize.
Utilization of CPU is close to the threshold.
The app has a high performance risk for the phone manufacturer(s) Lenovo, YU, Micromax, Panasonic. Check coverage report for more details.
10 tests need immediate attention. View performance graph.
Consider re-merging the code from build v1.1.1, CPU score was 3.4
Build v1.1.1 did better in Network . Spikes in Network contributed to score drop by 8%
Consider re-merging the code from build v1.1.1, Memory score was 3.2
74.60 MB of App Dalvik utilized by activity com.cmcm.adsdk.interstitial.PicksInterstitialActivity. View details
Testability: Providing login / sign-up details could very well improve depth of bot clicks
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!
Your average App Dalvik usage surged by 34.41%, Your memory score is 2.7
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
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
Optimize the app to render elements at 60 FPS for buttery smooth experience.
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
Printing logs on callbacks would make debugging easy for tests run in our platform
Avoid wake-locks in background, using Batch and schedulers APIs such as GCM, Job schedulers could reduce wake-locks
Unlock more fixes

Screen Coverage

competition benchmark

This app is ranked #1795 in Lifestyle

1790
1791
1792
1793
1794
back-to-top