App Quality Dashboard

PicsArt

2.1 / 5

Chhi Score

This app is performing

Average

Medium Risk

/5

High Risk

/5

Good 

/5

Medium Risk

/5

#

 

Category

Rank

  • Install time: Icon 65.57 Sec
  • Launch time: Icon 1.20 Sec
  • Application size: Icon 55.20 MB
  • Last tested on : 18/05/2017
  • Build ID
    :   v9.6.1
  • Chhi Score
    :   2.1
  • Change Rate
    :   0%

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.

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

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

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

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

Potential risk in CPU: Utilization has gone up by 21.43% compared to build v9.5.0

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

7 tests need immediate attention. View performance graph.

The app's Memory score has improved by 3.12% compared to build v9.5.0! Good job!

The app's Network score has improved by 166.67% compared to build v9.5.0! Good job!

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

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

358 apps having similar CPU load have low Chhi Scores

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

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

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

Caching: Use LruCache for data caching to optimize memory usage

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

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

Network utilization on Lenovo A6000 exceeded 1024 KB, you might want to consider bringing it down

75.40 MB of App Dalvik utilized by activity com.picsart.studio.profile.FindInterestsActivity. View details

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

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

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

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

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

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

Well done, Network consumption has come down by 61.7 % compared to build v9.5.0

Screen coverage

Test Flows YU Yuphoria Lava Iris X8 Zenfone 2 Laser Lenovo A6000

Install app

  • Risk

  • Risk

  • Risk

  • Risk

Scenario 1

  • Risk

  • Risk

Scenario 2

  • Risk

competition benchmark

This app is ranked #829 in Photography

824
825
826
827
828
back-to-top