App Quality Dashboard

Morningstar Events

2.4 / 5

Chhi Score

This app is performing

Average

Medium Risk

/5

Medium Risk

/5

Good 

/5

High Risk

/5

#

 

Category

Rank

  • Install time: Icon 43.35 Sec
  • Launch time: Icon 2.75 Sec
  • Application size: Icon 26.06 MB
  • Last tested on : 12/04/2017
  • Build ID
    :   v5.9
  • Chhi Score
    :   2.4
  • Change Rate
    :   -38.46 %

What to fix?

Build v5.6.1 did better in CPU . Spikes in CPU contributed to score drop by 6.45%

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

Potential risk in Network: Utilization has gone up by74.47% compared to build v5.6.1

4 Risk(s) are due to Data Sent/Received in Network 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.

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

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

Build v5.6.1 did better in Memory . Spikes in Memory contributed to score drop by 2.44%

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

Consider re-merging the code from build v5.6.1, Network score was 4.7

Utilization of CPU is close to the threshold.

9 tests need immediate attention. View performance graph.

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

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

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

Total Network data consumed was 4760.39KB 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

Network utilization on Karbonn Titanium Machfive exceeded 1024 KB, you might want to consider bringing it down

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

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

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

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

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

Caching: Use LruCache for data caching to optimize memory usage

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.

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

50.78 MB of App Dalvik utilized by activity com.crowdcompass.bearing.client.eventdirectory.controller.EventDirectoryController. View details

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

Network utilization on YU Yuphoria exceeded 1024 KB, you might want to consider bringing it down

Your average App Dalvik usage surged by 5.56%, Your memory score is 4.0

competition benchmark

This app is ranked #1015 in Business

1010
1011
1012
1013
1014
back-to-top