App Quality Dashboard

U-Dictionary

1.7 / 5

Chhi Score

This app is performing

Poor

Medium Risk

/5

High Risk

/5

Good 

/5

Medium Risk

/5

#

 

Category

Rank

  • Install time: Icon 12.23 Sec
  • Launch time: Icon 0.54 Sec
  • Application size: Icon 5.03 MB
  • Last tested on : 26/04/2017
  • Build ID
    :   v2.6.0
  • Chhi Score
    :   1.7
  • Change Rate
    :   -46.88 %

What to fix?

Build v2.5.1 did better in Network . Spikes in Network contributed to score drop by 57.45%

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

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

Build v2.5.1 did better in Memory . Spikes in Memory contributed to score drop by 16.67%

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

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

Potential risk in CPU: Utilization has gone up by 25% compared to build v2.5.1

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.

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

9 tests need immediate attention. View performance graph.

App size increased by 11.53% See how to optimize.

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

Consider re-merging the code from build v2.5.1, CPU score was 2.0

Consider re-merging the code from build v2.5.1, Network score was 4.7

Consider re-merging the code from build v2.5.1, Memory score was 3.0

Utilization of CPU is close to the threshold.

Fix Oncreate() if the launch time is exceeding more than 3.2 secs. Try deflating views and layouts to optimize.

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

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

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

App makes 2154.88 KB of network requests. Moving this to a background thread will improve load speed. View details

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

71.42 MB of App Dalvik utilized by activity com.youdao.hindict.activity.MainActivity. View details

There is high probability of identifying risks running the apps with conditions

Network utilization on Samsung Duos Galaxy J7 exceeded 1024 KB, you might want to consider bringing it down

Your average App Dalvik usage surged by 1.09%, Your memory score is 2.5

Network utilization on Panasonic P55 exceeded 1024 KB, you might want to consider bringing it down

Total Network data consumed was 2154.88KB in Samsung Duos Galaxy J7 , This indicates the app will take 10-15 seconds on 2G network and 8-9 seconds on 3G network to load! View details

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

Testability: Providing login / sign-up details could very well improve depth of bot clicks

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

Caching: Use LruCache for data caching to optimize memory usage

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

282 apps having similar CPU load have low Chhi Scores

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

Screen Coverage

competition benchmark

This app is ranked #2050 in Education

2045
2046
2047
2048
2049
back-to-top