App Quality Dashboard

NUR.KZ

0.3 / 5

Chhi Score

This app is performing

Poor

High Risk

/5

High Risk

/5

Good 

/5

Medium Risk

/5

#

 

Category

Rank

  • Install time: Icon 17.11 Sec
  • Launch time: Icon 8.20 Sec
  • Application size: Icon 6.25 MB
  • Last tested on : 18/03/2017
  • Build ID
    :   v5.1.10
  • Chhi Score
    :   0.3
  • 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

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

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

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

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

Your App CPU 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

Build v5.1.9 did better in Network . Spikes in Network contributed to score drop by 12.5%

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.

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

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

27 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.

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

Consider re-merging the code from build v5.1.9, Network score was 4.0

12 Risk(s) are due to App Dalvik in Memory exceeding the threshold.

27 tests need immediate attention. View performance graph.

54.00 MB of App Dalvik utilized by activity 2736. View details

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

435 apps having similar CPU load have low Chhi Scores

Caching: Use LruCache for data caching to optimize memory usage

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

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

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

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

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!

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

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

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

Screen coverage

competition benchmark

This app is ranked #1379 in News & Magazines

1374
1375
1376
1377
1378
back-to-top