App Quality Dashboard

Animator

2.3 / 5

Chhi Score

This app is performing

Average

Medium Risk

/5

High Risk

/5

Good 

/5

High Risk

/5

#

 

Category

Rank

  • Install time: Icon 39.13 Sec
  • Launch time: Icon 1.65 Sec
  • Application size: Icon 41.43 MB
  • Last tested on : 17/06/2017
  • Build ID
    :   v1.3.1
  • Chhi Score
    :   2.3
  • Change Rate
    :   -41.03 %

What to fix?

Fixing Network risks could drastically improve Chhi Score. There are 6 Network risks.

App launch time went up by INF% initlizate network calls after few seconds of loading the resources. View details

Potential risk in CPU: Utilization has gone up by 36% compared to build v1.2.2

Fixing CPU risks could drastically improve Chhi Score. There are 6 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

Potential risk in Network: Utilization has gone up by75.51% compared to build v1.2.2

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

Build v1.2.2 did better in Memory . Spikes in Memory contributed to score drop by 7.89%

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.

Consider re-merging the code from build v1.2.2, CPU score was 2.5

Consider re-merging the code from build v1.2.2, Network score was 4.9

Utilization of CPU is close to the threshold.

13 tests need immediate attention. View performance graph.

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

App size increased by 15.34% See how to optimize.

6 Risk(s) are due to CPU Load in CPU exceeding the threshold.

Fix Oncreate() if the launch time is exceeding more than 3.2 secs. Try deflating views and layouts to optimize.

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

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

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

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

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

42 apps having similar CPU load have low Chhi Scores

Caching: Use LruCache for data caching to optimize memory usage

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

119.32 MB of App Dalvik utilized by activity com.picsart.animator.ui.activity.ImagePickerActivity. View details

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

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

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

Network utilization on LYF-WATER exceeded 1024 KB, you might want to consider bringing it down

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

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

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

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

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

Total Network data consumed was 33165.61KB 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

Screen Coverage

competition benchmark

This app is ranked #76 in Art & Design

71
72
73
74
75
back-to-top