App Quality Dashboard

Pulse

0.8 / 5

Chhi Score

This app is performing

Poor

Medium Risk

/5

High Risk

/5

Good 

/5

High Risk

/5

#

 

Category

Rank

  • Install time: Icon 49.33 Sec
  • Launch time: Icon 1.56 Sec
  • Application size: Icon 47.15 MB
  • Last tested on : 18/05/2017
  • Build ID
    :   v1.2.114
  • Chhi Score
    :   0.8
  • Change Rate
    :   -42.86 %

What to fix?

3 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 v1.2.100

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

Build v1.2.100 did better in Memory . Spikes in Memory contributed to score drop by 4.76%

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

Potential risk in CPU: Utilization has gone up by 41.18% compared to build v1.2.100

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

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

Consider re-merging the code from build v1.2.100, CPU score was 1.7

Consider re-merging the code from build v1.2.100, Network score was 4.3

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

9 tests need immediate attention. View performance graph.

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

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

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

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

56.49 MB of App Dalvik utilized by activity org.chromium.chrome.browser.ChromeTabbedActivity. View details

Caching: Use LruCache for data caching to optimize memory usage

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

Your average App Dalvik usage surged by 14.64%, Your memory score is 2.0

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

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

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

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

98 apps having similar CPU load have low Chhi Scores

Network utilization on Karbonn Titanium Machfive 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

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

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

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 #605 in Communication

600
601
602
603
604
back-to-top