App Quality Dashboard

MediBang Paint

1.1 / 5

Chhi Score

This app is performing

Poor

Medium Risk

/5

High Risk

/5

Good 

/5

Medium Risk

/5

#

 

Category

Rank

  • Install time: Icon 16.68 Sec
  • Launch time: Icon 2.17 Sec
  • Application size: Icon 10.07 MB
  • Last tested on : 20/04/2017
  • Build ID
    :   v11.0
  • Chhi Score
    :   1.1
  • Change Rate
    :   -72.5 %

What to fix?

Potential risk in CPU: Utilization has gone up by 56.52% compared to build v10.2

Build v10.2 did better in Memory . Spikes in Memory contributed to score drop by 5.41%

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

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

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.

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

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

1 Risk(s) are due to Data Sent/Received in Network exceeding the threshold.

1 Risk(s) are due to App Total in Memory exceeding the threshold.

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

31 tests need immediate attention. View performance graph.

Utilization of Network is close to the threshold.

Utilization of Memory is close to the threshold.

Consider re-merging the code from build v10.2, CPU score was 2.3

Utilization of CPU is close to the threshold.

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

42 apps having similar CPU load have low Chhi Scores

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

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.

Coverage: Android version coverage for reports will range between 5.1.1 to 7.1.2

Network utilization on Motorola Moto E (2nd gen) exceeded 1024 KB, you might want to consider bringing it down

Follow simple UI hierarchy by reducing nested layouts to Relative layouts.

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

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

Total Network data consumed was 1217.91KB in Motorola Moto E (2nd gen) , This indicates the app will take 10-15 seconds on 2G network and 8-9 seconds on 3G network to load! View details

App makes 1217.91 KB of network requests. Moving this to a background thread will improve load speed. View details

61.13 MB of App Dalvik utilized by activity com.medibang.android.paint.tablet.ui.activity.WalkthroughActivity. View details

Your average App Dalvik usage surged by 6.66%, Your memory score is 3.5

There is high probability of identifying risks running the apps with conditions

Caching: Use LruCache for data caching to optimize memory usage

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

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

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

Screen coverage

competition benchmark

This app is ranked #121 in Art & Design

116
117
118
119
120
back-to-top