App Quality Dashboard

Phrasal Verbs

1.6 / 5

Chhi Score

This app is performing

Poor

Medium Risk

/5

High Risk

/5

Good 

/5

High Risk

/5

#

 

Category

Rank

  • Install time: Icon 9.15 Sec
  • Launch time: Icon 1.09 Sec
  • Application size: --- 2.36 MB
  • Last tested on : 01/05/2017
  • Build ID
    :   v1.1
  • Chhi Score
    :   1.6
  • Change Rate
    :   -40.74 %

What to fix?

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

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 1.0 did better in Memory . Spikes in Memory contributed to score drop by 4.17%

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

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

Potential risk in CPU: Utilization has gone up by 26.32% compared to build 1.0

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

Potential risk in Network: Utilization has gone up by72.09% compared to build 1.0

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

Consider re-merging the code from build 1.0, CPU score was 1.9

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

Utilization of CPU is close to the threshold.

13 tests need immediate attention. View performance graph.

Consider re-merging the code from build 1.0, Network score was 4.3

App makes 3174.09 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

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

Coverage: Android version coverage for reports will range between 5.1.1 to 7.1.2

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.

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

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

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

Your average App Dalvik usage surged by 3.32%, Your memory score is 2.3

Network utilization on Karbonn Titanium Machfive exceeded 1024 KB, you might want to consider bringing it down

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

Network utilization on Zenfone 2 Laser exceeded 1024 KB, you might want to consider bringing it down

25.82 MB of App Dalvik utilized by activity com.sevenlynx.phrasal.verbs.MainActivity. View details

282 apps having similar CPU load have low Chhi Scores

Total Network data consumed was 3174.09KB in Zenfone 2 Laser , This indicates the app will take 10-15 seconds on 2G network and 8-9 seconds on 3G network to load! View details

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

Avoid wake-locks in background, using Batch and schedulers APIs such as GCM, Job schedulers could reduce wake-locks

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

Screen Coverage

competition benchmark

This app is ranked #2093 in Education

2088
2089
2090
2091
2092
back-to-top