App Quality Dashboard

whatsapp Scan

2.9 / 5

Chhi Score

This app is performing

Average

Medium Risk

/5

Medium Risk

/5

Good 

/5

Medium Risk

/5

#

 

Category

Rank

  • Install time: Icon 8.25 Sec
  • Launch time: Icon 1.91 Sec
  • Application size: Icon 2.90 MB
  • Last tested on : 03/04/2017
  • Build ID
    :   v1.5
  • Chhi Score
    :   2.9
  • Change Rate
    :   +81.25 %

What to fix?

Fixing CPU risks could drastically improve Chhi Score. There are 13 CPU 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.

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

App launch time went up by 768.18% initlizate network calls after few seconds of loading the resources. View details

9 Risk(s) are due to App PSS in Memory exceeding the threshold. See how to optimize memory and remove 9 High Risk(s).

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

1 Risk(s) are due to App Total in Memory exceeding the threshold.

The app's Network score has improved by 50% compared to build v1.2! Good job!

Utilization of CPU is close to the threshold.

Utilization of Memory is close to the threshold.

Utilization of Network is close to the threshold.

The app's CPU score has improved by 26.67% compared to build v1.2! Good job!

13 tests need immediate attention. View performance graph.

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

The app's Memory score has improved by 4.35% compared to build v1.2! Good job!

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

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

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

Caching: Use LruCache for data caching to optimize memory usage

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

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

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

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

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

42.97 MB of App Dalvik utilized by activity com.google.android.gms.ads.AdActivity. View details

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

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

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

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

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

Total Network data consumed was 8277.41KB in Lenovo VIBE K4 Note , 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.

Well done, Network consumption has come down by 51.21 % compared to build v1.2

Screen coverage

Test Flows YU Yuphoria Lava Iris X8 Panasonic P55 Zenfone 2 Laser Micromax Canvas A1 Lenovo VIBE K4 Note Samsung Duos Galaxy J7

Install app

  • Risk

  • Success

  • Risk

  • Risk

  • Risk

  • Risk

  • Success

Scenario 1

  • Risk

  • Success

  • Risk

  • Risk

  • Risk

  • Risk

Scenario 2

  • Risk

  • Risk

  • Risk

competition benchmark

This app is ranked #464 in Communication

459
460
461
462
463
back-to-top