App Quality Dashboard

PSC Exam Winner

2.3 / 5

Chhi Score

This app is performing

Average

Medium Risk

/5

Medium Risk

/5

Good 

/5

High Risk

/5

#

 

Category

Rank

  • Install time: Icon 23.14 Sec
  • Launch time: Icon 7.43 Sec
  • Application size: Icon 10.00 MB
  • Last tested on : 14/06/2017
  • Build ID
    :   v1.10
  • Chhi Score
    :   2.3
  • Change Rate
    :   0%

What to fix?

Build v1.9 did better in CPU . Spikes in CPU contributed to score drop by 9.52%

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

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

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.

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

Build v1.9 did better in Memory . Spikes in Memory contributed to score drop by 5.41%

Utilization of CPU is close to the threshold.

19 tests need immediate attention. View performance graph.

1 Risk(s) are due to CPU Load in CPU exceeding the threshold.

Utilization of Network is close to the threshold.

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

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

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

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

Network utilization on Zenfone 2 Laser exceeded 1024 KB, you might want to consider bringing it down

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

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

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

Your average App Dalvik usage surged by 3.32%, Your memory score is 3.5

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

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

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

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

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

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

57.81 MB of App Dalvik utilized by activity com.appyet.activity.ImageViewerActivity. View details

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

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

competition benchmark

This app is ranked #1734 in Education

1729
1730
1731
1732
1733
back-to-top