App Quality Dashboard

Hooked

2.5 / 5

Chhi Score

This app is performing

Average

Good

/5

Medium Risk

/5

Good 

/5

High Risk

/5

#

 

Category

Rank

  • Install time: Icon 10.35 Sec
  • Launch time: Icon 1.23 Sec
  • Application size: Icon 3.80 MB
  • Last tested on : 10/06/2017
  • Build ID
    :   v1.31
  • Chhi Score
    :   2.5
  • Change Rate
    :   -40.48 %

What to fix?

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

1 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.

Potential risk in Network: Utilization has gone up by72.73% compared to build v1.30

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

Build v1.30 did better in CPU . Spikes in CPU contributed to score drop by 21.95%

7 tests need immediate attention. View performance graph.

Utilization of CPU is close to the threshold.

Consider re-merging the code from build v1.30, Network score was 4.4

Build v1.30 did better in Memory . Spikes in Memory contributed to score drop by 2.38%

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

Consider re-merging the code from build v1.30, CPU score was 4.1

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

Network utilization on Motorola Moto E (2nd gen) exceeded 1024 KB, you might want to consider bringing it down

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

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

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

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

Caching: Use LruCache for data caching to optimize memory usage

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.

Your average App Dalvik usage surged by 6.84%, Your memory score is 4.1

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

55.32 MB of App Dalvik utilized by activity tv.telepathic.hooked.activities.MainActivity. View details

Total Network data consumed was 5431.52KB in Motorola Moto E (2nd gen) , This indicates the app will take 10-15 seconds on 2G network and 8-9 seconds on 3G network to load! View details

Network utilization on Lenovo A6000 exceeded 1024 KB, you might want to consider bringing it down

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

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

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

Screen Coverage

competition benchmark

This app is ranked #1007 in Books & Reference

1002
1003
1004
1005
1006
back-to-top