App Quality Dashboard

DR Radio

0.2 / 5

Chhi Score

This app is performing

Poor

Memory

High Risk

/5

CPU

Medium Risk

/5

crash

Medium  Risk

/5

network

Good

/5

Competition

#

 

Category

Rank

  • Install time: 21.29 Sec
  • Launch time: 2.64 Sec
  • Application size : 16.29 MB
  • Last tested on : 07/05/2017
  • Build ID
    :   v5.0.1
  • Chhi Score
    :   0.2
  • Change Rate
    :   0%

Insights (29)

What to fix?

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.
Must fix: App crashed because of 7101): FATAL EXCEPTION: main 7101): Process: dk.dr.radio PID: 7101 7101): java.lang.IllegalArgu... Users with phone manufactured by Micromax might experience a crash on their phone!. Fix now!
Fixing CPU risks could drastically improve Chhi Score. There are 12 CPU risks.
Your App Memory 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
17 Risk(s) are due to App PSS in Memory exceeding the threshold. See how to optimize memory and remove 17 High Risk(s).
12 Risk(s) are due to Threads in CPU exceeding the threshold.
Utilization of CPU is close to the threshold.
The app has a high performance risk for the phone manufacturer(s) Asus, Karbonn, Lenovo, Panasonic, Motorola, YU, LYF, Micromax. Check coverage report for more details.
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.
17 tests need immediate attention. View performance graph.
Utilization of Memory is close to the threshold.
The app's memory score is 0.5 due to high memory utilization. Needs to be fixed as priority.
17 Risk(s) are due to App Total in Memory exceeding the threshold.
13 Risk(s) are due to App Dalvik in Memory exceeding the threshold.
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.
Do not initialize objects that aren't necessary during launch times. Moving to singleton pattern helps
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!
Caching: Use LruCache for data caching to optimize memory usage
Testability: Providing login / sign-up details could very well improve depth of bot clicks
68.00 MB of App Dalvik utilized by activity 15960. View details
Fix & Optimize launch time using Flatbuffers for storage and rendering performance.
Printing logs on callbacks would make debugging easy for tests run in our platform
There is high probability of identifying risks running the apps with conditions
Upload APKs with and without 3rd Party SDKs to monitor and optimize the impact of app performance
The app has crashed on few device(s)! View details
Fix Oncreate() if the launch time is exceeding more than 3.2 secs. Try deflating views and layouts to optimize.
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 #973 in Music & Audio

968
969
970
971
972
back-to-top