App Quality Dashboard

Name Art

3.6 / 5

Chhi Score

This app is performing


Medium Risk


Medium Risk




Medium Risk






  • Install time: --- 6.68 Sec
  • Launch time: Icon 1.71 Sec
  • Application size: Icon 4.55 MB
  • Last tested on : 06/05/2017
  • Build ID
    :   v2.1
  • Chhi Score
    :   3.6
  • Change Rate
    :   -2.7 %

What to fix?

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

Build v2.0 did better in Memory . Spikes in Memory contributed to score drop by 8.33%

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

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 v2.0 did better in CPU . Spikes in CPU contributed to score drop by 25%

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

18 tests need immediate attention. View performance graph.

Consider re-merging the code from build v2.0, CPU score was 2.8

Build v2.0 did better in Network . Spikes in Network contributed to score drop by 20.41%

Utilization of CPU is close to the threshold.

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

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

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

Caching: Use LruCache for data caching to optimize memory usage

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

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!

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

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

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

89.34 MB of App Dalvik utilized by activity View details

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

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

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

Screen Coverage

competition benchmark

This app is ranked #456 in Photography