App Quality Dashboard

Mush

1.0 / 5

Chhi Score

This app is performing

Poor

High Risk

/5

Medium Risk

/5

Good 

/5

Good

/5

#

 

Category

Rank

  • Install time: Icon 34.57 Sec
  • Launch time: Icon 1.27 Sec
  • Application size: Icon 51.05 MB
  • Last tested on : 27/03/2017
  • Build ID
    :   v1.28.4119
  • Chhi Score
    :   1.0
  • Change Rate
    :   -54.55 %

What to fix?

Fixing CPU risks could drastically improve Chhi Score. There are 2 CPU risks.

Build v1.26.3620 did better in CPU . Spikes in CPU contributed to score drop by 20.69%

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.

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

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

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

Potential risk in Memory: Utilization has gone up by30% compared to build v1.26.3620

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.

Consider re-merging the code from build v1.26.3620, CPU score was 2.9

The app's memory score is 1.4 due to high memory utilization. Needs to be fixed as priority.

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

App size increased by 17.38% See how to optimize.

Consider re-merging the code from build v1.26.3620, Memory score was 2.0

7 tests need immediate attention. View performance graph.

Utilization of CPU is close to the threshold.

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

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

Below 10 MB approach would increase app installs in crowded markets such as India, China and Russia!

Your average App Dalvik usage surged by 21.79%, Your memory score is 1.4

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

44.14 MB of App Dalvik utilized by activity com.mushuk.mushapp.MainActivity. View details

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.

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

Fix & Optimize launch time using Flatbuffers for storage and rendering performance.

Do not initialize objects that aren't necessary during launch times. Moving to singleton pattern helps

Caching: Use LruCache for data caching to optimize memory usage

Avoid wake-locks in background, using Batch and schedulers APIs such as GCM, Job schedulers could reduce wake-locks

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

The app's Network score has improved by 2.13% compared to build v1.26.3620! Good job!

Screen coverage

competition benchmark

This app is ranked #86 in Parenting

81
82
83
84
85
back-to-top