App Quality Dashboard

Orchid Flower

2.6 / 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 8.60 Sec
  • Launch time: Icon 0.24 Sec
  • Application size: Icon 3.51 MB
  • Last tested on : 15/06/2017
  • Build ID
    :   v1.1.7
  • Chhi Score
    :   2.6
  • Change Rate
    :   -16.13 %

Insights (26)

What to fix?

Build v1.1.5 did better in CPU . Spikes in CPU contributed to score drop by 29.41%
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.
2 Risk(s) are due to App PSS in Memory exceeding the threshold. See how to optimize memory and remove 2 High Risk(s).
Build v1.1.5 did better in Memory . Spikes in Memory contributed to score drop by 23.33%
2 tests need immediate attention. View performance graph.
Utilization of Memory is close to the threshold.
Consider re-merging the code from build v1.1.5, Memory score was 3.0
Build v1.1.5 did better in Network . Spikes in Network contributed to score drop by 8%
App size increased by 40.4% See how to optimize.
Consider re-merging the code from build v1.1.5, CPU score was 3.4
Utilization of CPU is close to the threshold.
The app has a high performance risk for the phone manufacturer(s) Asus. Check coverage report for more details.
Coverage: Android version coverage for reports will range between 5.1.1 to 7.1.2
Below 10 MB approach would increase app installs in crowded markets such as India, China and Russia!
Printing logs on callbacks would make debugging easy for tests run in our platform
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
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
Fix Oncreate() if the launch time is exceeding more than 3.2 secs. Try deflating views and layouts to optimize.
Follow simple UI hierarchy by reducing nested layouts to Relative layouts.
Fix & Optimize launch time using Flatbuffers for storage and rendering performance.
There is high probability of identifying risks running the apps with conditions
39.23 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
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 #2168 in Lifestyle

2163
2164
2165
2166
2167
back-to-top