App Quality Dashboard

CarAndBike

0.4 / 5

Chhi Score

This app is performing

Poor

High Risk

/5

Medium Risk

/5

High  Risk

/5

High Risk

/5

#

 

Category

Rank

  • Install time: 14.40 Sec
  • Launch time: 1.50 Sec
  • Application size : 9.77 MB
  • Last tested on : 17/04/2017
  • Build ID
    :   v1.01
  • Chhi Score
    :   0.4
  • Change Rate
    :   0%

What to fix?

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

Your App Memory 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

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

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

2 Risk(s) are due to Threads in CPU 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.

Must fix: App crashed because of 7803): FATAL EXCEPTION: main 7803): Process: com.ndtv.auto PID: 7803 7803): java.lang.IllegalSt... Users with phone manufactured by Lenovo might experience a crash on their phone!. Fix now!

Must fix: App crashed because of 7803): FATAL EXCEPTION: main 7803): Process: com.ndtv.auto PID: 7803 7803): java.lang.IllegalSt... Users with phone manufactured by Samsung might experience a crash on their phone!. Fix now!

2 tests need immediate attention. View performance graph.

The app's memory score is 1.3 due to high memory utilization. Needs to be fixed as priority.

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

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

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

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

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

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

Caching: Use LruCache for data caching to optimize memory usage

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

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

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

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

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

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.

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

52.72 MB of App Dalvik utilized by activity com.ndtv.auto.home.HomeActivity. View details

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

Network utilization on Samsung Galaxy J7 exceeded 1024 KB, you might want to consider bringing it down

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

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 #117 in Auto & Vehicles

112
113
114
115
116
back-to-top