App Quality Dashboard

How to Draw Youkai

1.2 / 5

Chhi Score

This app is performing

Poor

High Risk

/5

Medium Risk

/5

Good 

/5

High Risk

/5

#

 

Category

Rank

  • Install time: 10.07 Sec
  • Launch time: 3.00 Sec
  • Application size : 5.50 MB
  • Last tested on : 15/03/2017
  • Build ID
    :   v1.0
  • Chhi Score
    :   1.2
  • Change Rate
    :   0%

What to fix?

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

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

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

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

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

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

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

14 tests need immediate attention. View performance graph.

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

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.

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

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

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

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

App makes 4166.81 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

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

55.99 MB of App Dalvik utilized by activity com.andromo.dev421413.app579881.Dashboard_000. View details

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

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

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

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

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

Caching: Use LruCache for data caching to optimize memory usage

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

Network utilization on Motorola Moto E (2nd gen) 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

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

Screen Coverage

competition benchmark

This app is ranked #2226 in Education

2221
2222
2223
2224
2225
back-to-top