App Quality Dashboard

Kamusku

1.4 / 5

Chhi Score

This app is performing

Poor

Memory

Medium Risk

/5

CPU

High Risk

/5

crash

Good 

/5

network

Good

/5

Competition

#

 

Category

Rank

  • Install time: Icon 13.60 Sec
  • Launch time: Icon 4.26 Sec
  • Application size: Icon 9.60 MB
  • Last tested on : 25/04/2017
  • Build ID
    :   v6.4.3
  • Chhi Score
    :   1.4
  • Change Rate
    :   +250 %

Insights (27)

What to fix?

App launch time went up by 20.12% initlizate network calls after few seconds of loading the resources. View details
23 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.
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
Fixing CPU risks could drastically improve Chhi Score. There are 23 CPU risks.
Potential risk in CPU: Utilization has gone up by 25% compared to build v6.4.2
The app's Memory score has improved by 100% compared to build v6.4.2! Good job!
Consider re-merging the code from build v6.4.2, CPU score was 2.0
The app took 4.26 seconds to load on Android OS version 5.0.2. Usually anything more than 3.2 seconds results in user drops. View details
23 tests need immediate attention. View performance graph.
The app has a high performance risk for the phone manufacturer(s) Panasonic, Micromax, Samsung, Lava, YU, Lenovo, LYF, Asus. Check coverage report for more details.
Follow simple UI hierarchy by reducing nested layouts to Relative layouts.
Optimize the app to render elements at 60 FPS for buttery smooth experience.
Fix & Optimize launch time using Flatbuffers for storage and rendering performance.
Printing logs on callbacks would make debugging easy for tests run in our platform
Caching: Use LruCache for data caching to optimize memory usage
Avoid wake-locks in background, using Batch and schedulers APIs such as GCM, Job schedulers could reduce wake-locks
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
Testability: Providing login / sign-up details could very well improve depth of bot clicks
318 apps having similar CPU load have low Chhi Scores
Do not initialize objects that aren't necessary during launch times. Moving to singleton pattern helps
Below 10 MB approach would increase app installs in crowded markets such as India, China and Russia!
59.88 MB of App Dalvik utilized by activity com.kodelokus.kamusku.MainActivity. View details
Upload APKs with and without 3rd Party SDKs to monitor and optimize the impact of app performance
The app's Network score has improved by 2.5% compared to build v6.4.2! Good job!
Unlock more fixes
competition benchmark

This app is ranked #1452 in Books & Reference

1447
1448
1449
1450
1451
back-to-top