WhatsApp

2.2 / 5

Chhi Score

This app is performing

Average

Medium Risk

/5

Medium Risk

/5

Medium  Risk

/5

Good

/5

#

 

Category

Rank

  • Install time: Icon 33.11 Sec
  • Launch time: Icon 2.06 Sec
  • Application size: Icon 30.97 MB
  • Last tested on : 10/10/2017
  • Build ID
    :   v2.17.351
  • Chhi Score
    :   2.2
  • Change Rate
    :   -33.33 %

What to fix?

Build v2.17.146 did better in Memory . Spikes in Memory contributed to score drop by 25%

Must fix: App crashed because of java.lang.RuntimeException: Performing stop of activity that is not resumed: {com.whatsapp/com.... Users with phone manufactured by Micromax might experience a crash on their phone!. Fix now!

Must fix: App crashed because of java.lang.RuntimeException: Performing stop of activity that is not resumed: {com.whatsapp/com.... Users with phone manufactured by Lenovo might experience a crash on their phone!. Fix now!

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.

Must fix: App crashed because of java.lang.RuntimeException: Performing stop of activity that is not resumed: {com.whatsapp/com.... Users with phone manufactured by Karbonn might experience a crash on their phone!. Fix now!

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

Build v2.17.146 did better in CPU . Spikes in CPU contributed to score drop by 26.92%

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

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

Utilization of CPU is close to the threshold.

Consider re-merging the code from build v2.17.146, CPU score was 2.6

Lenovo A6000, Samsung Duos Galaxy J7, Karbonn Titanium Machfive has moved from Good to Medium risk due to FAIL . View details

Build v2.17.146 did better in Network . Spikes in Network contributed to score drop by 2%

Consider re-merging the code from build v2.17.146, Memory score was 3.2

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

6 Risk(s) are due to CPU Load in CPU exceeding the threshold.

9 tests need immediate attention. View performance graph.

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

Caching: Use LruCache for data caching to optimize memory usage

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

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

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

31.82 MB of App Dalvik utilized by activity com.whatsapp.DescribeProblemActivity. View details

The app has crashed on few device(s)! View details

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

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

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

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

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

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

3 Tests crashed out of 18 Tests. Check where the app crashed. View details

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

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

Screen Coverage

competition benchmark

This app is ranked #507 in Communication

502
503
504
505
506
back-to-top