App Quality Dashboard

Learn To Draw

1.9 / 5

Chhi Score

This app is performing

Average

Memory

Medium Risk

/5

CPU

Medium Risk

/5

crash

Good 

/5

network

High Risk

/5

Competition

#

 

Category

Rank

  • Install time: Icon 26.59 Sec
  • Launch time: Icon 4.01 Sec
  • Application size: Icon 39.37 MB
  • Last tested on : 22/05/2017
  • Build ID
    :   v4.1
  • Chhi Score
    :   1.9
  • Change Rate
    :   0%

Insights (32)

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.
Build 2.9 did better in Memory . Spikes in Memory contributed to score drop by 3.45%
Potential risk in Network: Utilization has gone up by58.82% compared to build 2.9
App launch time went up by 33.83% initlizate network calls after few seconds of loading the resources. View details
Fixing CPU risks could drastically improve Chhi Score. There are 16 CPU risks.
3 Risk(s) are due to Data Sent/Received in Network exceeding the threshold.
16 Risk(s) are due to Threads in CPU exceeding the threshold.
16 tests need immediate attention. View performance graph.
Consider re-merging the code from build 2.9, Network score was 3.4
The app has a high performance risk for the phone manufacturer(s) LYF, Lava, Karbonn, Asus, Panasonic, Lenovo. Check coverage report for more details.
The app took 4.01 seconds to load on Android OS version 5.0.2. Usually anything more than 3.2 seconds results in user drops. View details
Utilization of Network is close to the threshold.
The app's CPU score has improved by 46.67% compared to build 2.9! Good job!
Network utilization on Zenfone 2 Laser exceeded 1024 KB, you might want to consider bringing it down
Testability: Providing login / sign-up details could very well improve depth of bot clicks
Below 10 MB approach would increase app installs in crowded markets such as India, China and Russia!
Fix Oncreate() if the launch time is exceeding more than 3.2 secs. Try deflating views and layouts to optimize.
There is high probability of identifying risks running the apps with conditions
App makes 1304.55 KB of network requests. Moving this to a background thread will improve load speed. View details
Network utilization on Lenovo A6000 exceeded 1024 KB, you might want to consider bringing it down
Printing logs on callbacks would make debugging easy for tests run in our platform
Total Network data consumed was 1304.55KB in Lenovo A6000 , This indicates the app will take 10-15 seconds on 2G network and 8-9 seconds on 3G network to load! View details
Do not initialize objects that aren't necessary during launch times. Moving to singleton pattern helps
Coverage: Android version coverage for reports will range between 5.1.1 to 7.1.2
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
Your average App Dalvik usage surged by 20.46%, Your memory score is 2.8
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.
43.58 MB of App Dalvik utilized by activity com.mobileapps.apps.LearnToDraw.draw.SplashActivity. View details
Caching: Use LruCache for data caching to optimize memory usage
Unlock more fixes

Screen Coverage

competition benchmark

This app is ranked #871 in Photography

866
867
868
869
870
back-to-top