App Quality Dashboard

Mirror Draw

1.3 / 5

Chhi Score

This app is performing

Poor

High Risk

/5

Medium Risk

/5

Good 

/5

High Risk

/5

#

 

Category

Rank

  • Install time: Icon 12.50 Sec
  • Launch time: Icon 0.36 Sec
  • Application size: Icon 4.17 MB
  • Last tested on : 24/03/2017
  • Build ID
    :   v1.1
  • Chhi Score
    :   1.3
  • Change Rate
    :   -18.75 %

What to fix?

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

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

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

Potential risk in Memory: Utilization has gone up by29.17% compared to build v1.0

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

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

Your App Memory 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 Data Sent/Received in Network exceeding the threshold.

Consider re-merging the code from build v1.0, Memory score was 2.4

Utilization of CPU is close to the threshold.

The app's memory score is 1.7 due to high memory utilization. Needs to be fixed as priority.

The app's CPU score has improved by 27.78% compared to build v1.0! Good job!

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

5 tests need immediate attention. View performance graph.

Make sure your App's PSS isn't too high. Freeing objects that aren't needed would reduce chances of getting unexpectedly killed by Android system.

1 Risk(s) are due to App Total in Memory exceeding the threshold.

Network utilization on Panasonic P55 exceeded 1024 KB, you might want to consider bringing it down

Total Network data consumed was 1143.60KB in Panasonic P55 , This indicates the app will take 10-15 seconds on 2G network and 8-9 seconds on 3G network to load! View details

Your average App Dalvik usage surged by 19.88%, Your memory score is 1.7

Caching: Use LruCache for data caching to optimize memory usage

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

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

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

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

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

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

Network utilization on Lenovo VIBE K4 Note 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

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

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

83.23 MB of App Dalvik utilized by activity com.studios.box.app.mirror.SplashActivity. View details

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

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

Screen coverage

competition benchmark

This app is ranked #119 in Art & Design

114
115
116
117
118
back-to-top