App Quality Dashboard

6 Kalma

1.3 / 5

Chhi Score

This app is performing

Poor

Medium Risk

/5

Medium Risk

/5

Good 

/5

Medium Risk

/5

#

 

Category

Rank

  • Install time: Icon 16.50 Sec
  • Launch time: Icon 0.74 Sec
  • Application size: Icon 6.10 MB
  • Last tested on : 26/02/2017
  • Build ID
    :   v2.8
  • Chhi Score
    :   1.3
  • Change Rate
    :   -18.75 %

What to fix?

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.

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

App launch time went up by 34.55% 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).

Build v2.7 did better in Memory . Spikes in Memory contributed to score drop by 25%

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

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

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

7 tests need immediate attention. View performance graph.

Utilization of Memory is close to the threshold.

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

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

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.

Consider re-merging the code from build v2.7, Memory score was 2.4

The app's Network score has improved by 100% compared to build v2.7! Good job!

The app's CPU score has improved by 12.5% compared to build v2.7! Good job!

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

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

Network utilization on YU Yuphoria 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

Your average App Dalvik usage surged by 2.37%, Your memory score is 1.8

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

Caching: Use LruCache for data caching to optimize memory usage

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

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

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

41.04 MB of App Dalvik utilized by activity com.cyberdesignz.kalmaofislam.MainActivity. View details

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

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

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

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

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

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

Well done, Network consumption has come down by 69.96 % compared to build v2.7

Screen coverage

competition benchmark

This app is ranked #1469 in Books & Reference

1464
1465
1466
1467
1468
back-to-top