App Quality Dashboard

Gadgets ३६०

0.2 / 5

Chhi Score

This app is performing


High Risk


Medium Risk


High  Risk








  • Install time: Icon 22.86 Sec
  • Launch time: Icon 1.17 Sec
  • Application size: Icon 8.89 MB
  • Last tested on : 27/03/2017
  • Build ID
    :   v1.15
  • Chhi Score
    :   0.2
  • Change Rate
    :   -93.33 %

What to fix?

Must fix: App crashed because of FATAL EXCEPTION: main Process: com.ndtv.gadgetshindi PID: 32143 java.lang.NullPointerException:... Users with phone manufactured by Panasonic might experience a crash on their phone!. Fix now!

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

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

Potential risk in Memory: Utilization has gone up by74.19% compared to build 1.14

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.

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

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

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

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

3 tests need immediate attention. View performance graph.

Consider re-merging the code from build 1.14, Memory score was 3.1

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

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

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.

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

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

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

Caching: Use LruCache for data caching to optimize memory usage

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

53.28 MB of App Dalvik utilized by activity com.ndtv.gadgetshindi.common.ui.HomeActivity. View details

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

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

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

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

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

The app's Network score has improved by 50% compared to build 1.14! Good job!

Well done, Network consumption has come down by 73.48 % compared to build 1.14

Screen Coverage

competition benchmark

This app is ranked #1412 in News & Magazines