App Quality Dashboard

Anagog Parking Navigator

1.7 / 5

Chhi Score

This app is performing

Poor

Medium Risk

/5

Medium Risk

/5

High  Risk

/5

Good

/5

#

 

Category

Rank

  • Install time: 7.78 Sec
  • Launch time: 7.24 Sec
  • Application size : 4.69 MB
  • Last tested on : 23/04/2017
  • Build ID
    :   v008
  • Chhi Score
    :   1.7
  • Change Rate
    :   0%

What to fix?

Must fix: App crashed because of FATAL EXCEPTION: main Process: com.anagog.parkingnavigator PID: 27423 java.lang.NullPointerExce... Users with phone manufactured by Asus might experience a crash on their phone!. Fix now!

Must fix: App crashed because of FATAL EXCEPTION: main Process: com.anagog.parkingnavigator PID: 27423 java.lang.NullPointerExce... Users with phone manufactured by Panasonic might experience a crash on their phone!. Fix now!

5 Risk(s) are due to App PSS in Memory exceeding the threshold. See how to optimize memory and remove 5 High Risk(s).

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

Must fix: App crashed because of FATAL EXCEPTION: main Process: com.anagog.parkingnavigator PID: 27423 java.lang.NullPointerExce... Users with phone manufactured by YU might experience a crash on their phone!. Fix now!

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

Must fix: App crashed because of FATAL EXCEPTION: main Process: com.anagog.parkingnavigator PID: 27423 java.lang.NullPointerExce... Users with phone manufactured by Motorola might experience a crash on their phone!. Fix now!

Must fix: App crashed because of FATAL EXCEPTION: main Process: com.anagog.parkingnavigator PID: 27423 java.lang.NullPointerExce... Users with phone manufactured by Micromax might experience a crash on their phone!. Fix now!

Must fix: App crashed because of FATAL EXCEPTION: main Process: com.anagog.parkingnavigator PID: 27423 java.lang.NullPointerExce... Users with phone manufactured by LYF might experience a crash on their phone!. Fix now!

Must fix: App crashed because of FATAL EXCEPTION: main Process: com.anagog.parkingnavigator PID: 27423 java.lang.NullPointerExce... Users with phone manufactured by Samsung might experience a crash on their phone!. Fix now!

Zenfone 2 Laser crashed at com.anagog.carma.MainFragment.activateLayer(MainFragment.java:5526) View details

Oops!, The app crashed on Motorola Moto E (2nd gen), Zenfone 2 Laser & more devices. View details

Motorola Moto E (2nd gen) crashed at com.anagog.carma.MainFragment.activateLayer(MainFragment.java:5526) View details

Must fix: App crashed because of FATAL EXCEPTION: main Process: com.anagog.parkingnavigator PID: 27423 java.lang.NullPointerExce... Users with phone manufactured by Karbonn might experience a crash on their phone!. Fix now!

Must fix: App crashed because of FATAL EXCEPTION: main Process: com.anagog.parkingnavigator PID: 27423 java.lang.NullPointerExce... Users with phone manufactured by Lenovo might experience a crash on their phone!. Fix now!

1 Risk(s) are due to App Total in Memory exceeding the threshold.

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

6 tests need immediate attention. View performance graph.

Utilization of CPU is close to the threshold.

The app took 7.24 seconds to load on Android OS version 6.0.1. Usually anything more than 3.2 seconds results in user drops. View details

Utilization of Memory is close to the threshold.

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

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

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.

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

62.87 MB of App Dalvik utilized by activity com.anagog.carma.MainActivity. View details

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

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

Caching: Use LruCache for data caching to optimize memory usage

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

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

9 Tests crashed out of 18 Tests. Check where the app crashed. View details

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.

Screen coverage

competition benchmark

This app is ranked #994 in Travel & Local

989
990
991
992
993
back-to-top