App Quality Dashboard

Nabız

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 21.00 Sec
  • Launch time: Icon 0.00 Sec
  • Application size: Icon 9.81 MB
  • Last tested on : 23/05/2017
  • Build ID
    :   v3.0
  • Chhi Score
    :   2.4
  • Change Rate
    :   0%

What to fix?

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

Potential risk in Network: Utilization has gone up by72.73% compared to build 2.6

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

1 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 3 CPU risks.

The app's CPU score has improved by 11.76% compared to build 2.6! Good job!

App size increased by 30.11% See how to optimize.

3 tests need immediate attention. View performance graph.

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

Consider re-merging the code from build 2.6, Network score was 4.4

Build 2.6 did better in Memory . Spikes in Memory contributed to score drop by 2.56%

Network utilization on LYF 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

32.35 MB of App Dalvik utilized by activity com.waveline.nabd.SlidingMenuManagerActivity. View details

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

Your average App Dalvik usage surged by 11.24%, Your memory score is 3.8

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.

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

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

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

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

Caching: Use LruCache for data caching to optimize memory usage

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

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

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

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.

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

Screen coverage

competition benchmark

This app is ranked #677 in News & Magazines

672
673
674
675
676
back-to-top