App Quality Dashboard

Photo Editor

3.9 / 5

Chhi Score

This app is performing


Medium Risk


Medium Risk










  • Install time: Icon 9.58 Sec
  • Launch time: Icon 5.62 Sec
  • Application size: Icon 4.30 MB
  • Last tested on : 25/04/2017
  • Build ID
    :   v2.4
  • Chhi Score
    :   3.9
  • Change Rate
    :   +56 %

What to fix?

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

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

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

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.

17 tests need immediate attention. View performance graph.

The app's CPU score has improved by 17.65% compared to build 2.3! Good job!

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

Build 2.3 did better in Memory . Spikes in Memory contributed to score drop by 2.44%

Utilization of CPU is close to the threshold.

The app took 5.62 seconds to load on Android OS version 5.0.2. Usually anything more than 3.2 seconds results in user drops. View details

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

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

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

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

40.83 MB of App Dalvik utilized by activity app.activity.MainActivity. View details

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

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

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.

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

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

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

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

The app's Network score has improved by 7.14% compared to build 2.3! Good job!

Well done, Network consumption has come down by 30.31 % compared to build 2.3

Screen Coverage

competition benchmark

This app is ranked #317 in Photography