App Quality Dashboard

Islam Kit

1.6 / 5

Chhi Score

This app is performing

Poor

Memory

Medium Risk

/5

CPU

Medium Risk

/5

crash

Good 

/5

network

Good

/5

Competition

#

 

Category

Rank

  • Install time: Icon 10.60 Sec
  • Launch time: Icon 1.48 Sec
  • Application size: Icon 9.58 MB
  • Last tested on : 27/03/2017
  • Build ID
    :   v1.3.2
  • Chhi Score
    :   1.6
  • Change Rate
    :   +33.33 %

Insights (24)

What to fix?

Fixing CPU risks could drastically improve Chhi Score. There are 9 CPU risks.
9 Risk(s) are due to Threads in CPU exceeding the threshold.
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's CPU score has improved by 63.64% compared to build 1.3.1! Good job!
The app's Memory score has improved by 41.18% compared to build 1.3.1! Good job!
Utilization of CPU is close to the threshold.
The app has a high performance risk for the phone manufacturer(s) Lenovo, Panasonic, Micromax, YU. Check coverage report for more details.
11 tests need immediate attention. View performance graph.
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
Fix Oncreate() if the launch time is exceeding more than 3.2 secs. Try deflating views and layouts to optimize.
Coverage: Android version coverage for reports will range between 5.1.1 to 7.1.2
Avoid wake-locks in background, using Batch and schedulers APIs such as GCM, Job schedulers could reduce wake-locks
70.16 MB of App Dalvik utilized by activity com.chaks.islamkit.main.activities.MainActivity. View details
Printing logs on callbacks would make debugging easy for tests run in our platform
Below 10 MB approach would increase app installs in crowded markets such as India, China and Russia!
Upload APKs with and without 3rd Party SDKs to monitor and optimize the impact of app performance
Do not initialize objects that aren't necessary during launch times. Moving to singleton pattern helps
Caching: Use LruCache for data caching to optimize memory usage
Fix & Optimize launch time using Flatbuffers for storage and rendering performance.
Optimize the app to render elements at 60 FPS for buttery smooth experience.
Follow simple UI hierarchy by reducing nested layouts to Relative layouts.
Well done, Network consumption has come down by 48.07 % compared to build 1.3.1
The app's Network score has improved by 9.52% compared to build 1.3.1! Good job!
Unlock more fixes

Screen Coverage

competition benchmark

This app is ranked #1374 in Books & Reference

1369
1370
1371
1372
1373
back-to-top