App Quality Dashboard

Whisper

1.1 / 5

Chhi Score

This app is performing

Poor

Medium Risk

/5

High Risk

/5

Good 

/5

High Risk

/5

#

 

Category

Rank

  • Install time: Icon 23.00 Sec
  • Launch time: Icon 6.18 Sec
  • Application size: Icon 16.11 MB
  • Last tested on : 22/03/2017
  • Build ID
    :   v8.0.0
  • Chhi Score
    :   1.1
  • Change Rate
    :   -50 %

What to fix?

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

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

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.

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

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

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

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

Build v7.9.1 did better in Memory . Spikes in Memory contributed to score drop by 3.03%

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

Potential risk in CPU: Utilization has gone up by 9.09% compared to build v7.9.1

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

The app took 6.18 seconds to load on Android OS version 5.0.2. Usually anything more than 3.2 seconds results in user drops. View details

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

27 tests need immediate attention. View performance graph.

Utilization of Memory is close to the threshold.

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

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

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

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

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.

Caching: Use LruCache for data caching to optimize memory usage

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

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

Your average App Dalvik usage surged by 12.46%, Your memory score is 3.2

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

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

213 apps having similar CPU load have low Chhi Scores

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

96.80 MB of App Dalvik utilized by activity sh.whisper.WMainActivity. View details

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

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

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

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

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

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

Screen coverage

competition benchmark

This app is ranked #734 in Social

729
730
731
732
733
back-to-top