App Quality Dashboard

Learn Malaysian Vocabulary

2.9 / 5

Chhi Score

This app is performing

Average

Memory

Medium Risk

/5

CPU

Medium Risk

/5

crash

Good 

/5

network

Good

/5

Competition

#

 

Category

Rank

  • Install time: Icon 12.92 Sec
  • Launch time: Icon 1.23 Sec
  • Application size: Icon 13.38 MB
  • Last tested on : 20/04/2017
  • Build ID
    :   v2.3.10
  • Chhi Score
    :   2.9
  • Change Rate
    :   -14.71 %

Insights (23)

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.
Build v2.3.4 did better in Memory . Spikes in Memory contributed to score drop by 15.63%
Consider re-merging the code from build v2.3.4, Memory score was 3.2
Utilization of CPU is close to the threshold.
The app has a high performance risk for the phone manufacturer(s) Asus, Lenovo, Samsung, YU, Motorola. Check coverage report for more details.
8 tests need immediate attention. View performance graph.
Build v2.3.4 did better in Network . Spikes in Network contributed to score drop by 2.04%
The app's CPU score has improved by 4.55% compared to build v2.3.4! Good job!
Do not initialize objects that aren't necessary during launch times. Moving to singleton pattern helps
Printing logs on callbacks would make debugging easy for tests run in our platform
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
Your average App Dalvik usage surged by 2.17%, Your memory score is 2.7
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.
28.58 MB of App Dalvik utilized by activity net.languagecourse.vt.ms.VocabularyTrainer. View details
Upload APKs with and without 3rd Party SDKs to monitor and optimize the impact of app performance
Fix & Optimize launch time using Flatbuffers for storage and rendering performance.
There is high probability of identifying risks running the apps with conditions
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.
Avoid wake-locks in background, using Batch and schedulers APIs such as GCM, Job schedulers could reduce wake-locks
Unlock more fixes

Screen Coverage

competition benchmark

This app is ranked #1327 in Education

1322
1323
1324
1325
1326
back-to-top