App Quality Dashboard

17

2.3 / 5

Chhi Score

This app is performing

Average

Memory

Medium Risk

/5

CPU

High Risk

/5

crash

Good 

/5

network

Good

/5

Competition

#

 

Category

Rank

  • Install time: Icon 73.10 Sec
  • Launch time: Icon 6.00 Sec
  • Application size: Icon 72.17 MB
  • Last tested on : 16/06/2017
  • Build ID
    :   v2.2.19.0
  • Chhi Score
    :   2.3
  • Change Rate
    :   -42.5 %

Insights (26)

What to fix?

Potential risk in CPU: Utilization has gone up by 32% compared to build v2.2.13.0
App launch time went up by 1176.6% initlizate network calls after few seconds of loading the resources. View details
17 Risk(s) are due to Threads in CPU 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.
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
Fixing CPU risks could drastically improve Chhi Score. There are 17 CPU risks.
The app has a high performance risk for the phone manufacturer(s) LYF, Micromax, Asus, Karbonn, Panasonic, Motorola, YU. Check coverage report for more details.
Consider re-merging the code from build v2.2.13.0, CPU score was 2.5
Utilization of CPU is close to the threshold.
18 tests need immediate attention. View performance graph.
The app took 6.00 seconds to load on Android OS version 5.0.2. Usually anything more than 3.2 seconds results in user drops. View details
Do not initialize objects that aren't necessary during launch times. Moving to singleton pattern helps
33.31 MB of App Dalvik utilized by activity com.machipopo.media17.activity.GuestModeActivity. View details
Caching: Use LruCache for data caching to optimize memory usage
There is high probability of identifying risks running the apps with conditions
Testability: Providing login / sign-up details could very well improve depth of bot clicks
Upload APKs with and without 3rd Party SDKs to monitor and optimize the impact of app performance
Below 10 MB approach would increase app installs in crowded markets such as India, China and Russia!
Avoid wake-locks in background, using Batch and schedulers APIs such as GCM, Job schedulers could reduce wake-locks
Printing logs on callbacks would make debugging easy for tests run in our platform
Fix & Optimize launch time using Flatbuffers for storage and rendering performance.
Follow simple UI hierarchy by reducing nested layouts to Relative layouts.
Coverage: Android version coverage for reports will range between 5.1.1 to 7.1.2
Optimize the app to render elements at 60 FPS for buttery smooth experience.
213 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.
Unlock more fixes

Screen Coverage

competition benchmark

This app is ranked #583 in Social

578
579
580
581
582
back-to-top