App Quality Dashboard

Gadgets ३६०

1.1 / 5

Chhi Score

This app is performing

Poor

Medium Risk

/5

Medium Risk

/5

Medium  Risk

/5

Good

/5

#

 

Category

Rank

  • Install time: Icon 20.57 Sec
  • Launch time: Icon 3.54 Sec
  • Application size: Icon 9.43 MB
  • Last tested on : 23/04/2017
  • Build ID
    :   v1.16
  • Chhi Score
    :   1.1
  • Change Rate
    :   -26.67 %

What to fix?

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

Samsung Duos Galaxy J7 crashed at android.support.v4.app.FragmentManagerImpl.checkStateLoss(FragmentManager.java:1538) View details

Panasonic P55 crashed at android.widget.SuggestionsAdapter.(SuggestionsAdapter.java:156) View details

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

Must fix: App crashed because of 735): FATAL EXCEPTION: main 735): Process: com.ndtv.gadgetshindi PID: 735 735): java.lang.Nul... 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 12 CPU risks.

App launch time went up by INF% initlizate network calls after few seconds of loading the resources. View details

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.

Oops!, The app crashed on Samsung Duos Galaxy J7, Panasonic P55 & more devices. View details

Build v1.15 did better in Memory . Spikes in Memory contributed to score drop by 25%

The app's CPU score has improved by 36.84% compared to build v1.15! Good job!

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

14 tests need immediate attention. View performance graph.

Utilization of CPU is close to the threshold.

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

Consider re-merging the code from build v1.15, Memory score was 2.8

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

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

6 Tests crashed out of 21 Tests. Check where the app crashed. View details

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

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

57.86 MB of App Dalvik utilized by activity com.google.android.gms.ads.AdActivity. View details

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

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

Caching: Use LruCache for data caching to optimize memory usage

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

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

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

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

The app's Network score has improved by 15% compared to build v1.15! Good job!

Well done, Network consumption has come down by 57.8 % compared to build v1.15

Screen Coverage

competition benchmark

This app is ranked #1298 in News & Magazines

1293
1294
1295
1296
1297
back-to-top