App Quality Dashboard

Talking Japanese Translator/Dictionary

1.3 / 5

Chhi Score

This app is performing

Poor

Memory

High Risk

/5

CPU

High Risk

/5

crash

Good 

/5

network

Medium Risk

/5

Competition

#

 

Category

Rank

  • Install time: Icon 55.96 Sec
  • Launch time: Icon 19.52 Sec
  • Application size: Icon 47.30 MB
  • Last tested on : 23/03/2017
  • Build ID
    :   v6.4.44
  • Chhi Score
    :   1.3
  • Change Rate
    :   -13.33 %

Insights (43)

What to fix?

Potential risk in CPU: Utilization has gone up by 9.09% compared to build v6.4.42
Fixing Network risks could drastically improve Chhi Score. There are 7 Network risks.
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
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
7 Risk(s) are due to Data Sent/Received in Network exceeding the threshold.
Fixing CPU risks could drastically improve Chhi Score. There are 24 CPU risks.
App launch time went up by 116.41% initlizate network calls after few seconds of loading the resources. View details
Potential risk in Memory: Utilization has gone up by22.73% compared to build v6.4.42
24 Risk(s) are due to Threads in CPU exceeding the threshold.
22 Risk(s) are due to App PSS in Memory exceeding the threshold. See how to optimize memory and remove 22 High Risk(s).
Do not initialize objects that aren't necessary during launch times. Moving to singleton pattern helps
The app has a high performance risk for the phone manufacturer(s) Lava, Asus, Lenovo, Panasonic, Karbonn, YU, LYF. Check coverage report for more details.
3 Risk(s) are due to App Total in Memory exceeding the threshold.
The app's memory score is 1.7 due to high memory utilization. Needs to be fixed as priority.
Utilization of Network is close to the threshold.
24 tests need immediate attention. View performance graph.
Utilization of Memory is close to the threshold.
Utilization of CPU is close to the threshold.
Consider re-merging the code from build v6.4.42, Memory score was 2.2
The app's Network score has improved by 4.55% compared to build v6.4.42! Good job!
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 took 19.52 seconds to load on Android OS version 5.0.2. Usually anything more than 3.2 seconds results in user drops. View details
Fix Oncreate() if the launch time is exceeding more than 3.2 secs. Try deflating views and layouts to optimize.
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
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
Fix & Optimize launch time using Flatbuffers for storage and rendering performance.
App makes 3557.55 KB of network requests. Moving this to a background thread will improve load speed. View details
There is high probability of identifying risks running the apps with conditions
Network utilization on Lenovo A6000 exceeded 1024 KB, you might want to consider bringing it down
Your average App Dalvik usage surged by 5.2%, Your memory score is 1.7
Caching: Use LruCache for data caching to optimize memory usage
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
Optimize the app to render elements at 60 FPS for buttery smooth experience.
Network utilization on Zenfone 2 Laser exceeded 1024 KB, you might want to consider bringing it down
62.48 MB of App Dalvik utilized by activity com.greenleaf.android.translator.MainActivity. View details
Testability: Providing login / sign-up details could very well improve depth of bot clicks
Printing logs on callbacks would make debugging easy for tests run in our platform
Total Network data consumed was 3557.55KB in Lenovo A6000 , This indicates the app will take 10-15 seconds on 2G network and 8-9 seconds on 3G network to load! View details
318 apps having similar CPU load have low Chhi Scores
Unlock more fixes

Screen coverage

competition benchmark

This app is ranked #1476 in Books & Reference

1471
1472
1473
1474
1475
back-to-top