App Quality Dashboard

Vua đầu bếp Việt

0.7 / 5

Chhi Score

This app is performing

Poor

Medium Risk

/5

Medium Risk

/5

High  Risk

/5

Medium Risk

/5

#

 

Category

Rank

  • Install time: 8.67 Sec
  • Launch time: 1.46 Sec
  • Application size : 4.59 MB
  • Last tested on : 23/04/2017
  • Build ID
    :   v1.2
  • Chhi Score
    :   0.7
  • Change Rate
    :   0%

What to fix?

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

Must fix: App crashed because of FATAL EXCEPTION: main Process: com.gamnhi.cookingstips PID: 10091 java.lang.NullPointerExceptio... Users with phone manufactured by Panasonic might experience a crash on their phone!. Fix now!

Must fix: App crashed because of FATAL EXCEPTION: main Process: com.gamnhi.cookingstips PID: 10091 java.lang.NullPointerExceptio... Users with phone manufactured by YU might experience a crash on their phone!. Fix now!

Must fix: App crashed because of FATAL EXCEPTION: main Process: com.gamnhi.cookingstips PID: 10091 java.lang.NullPointerExceptio... Users with phone manufactured by Samsung might experience a crash on their phone!. Fix now!

Must fix: App crashed because of FATAL EXCEPTION: main Process: com.gamnhi.cookingstips PID: 10091 java.lang.NullPointerExceptio... 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.gamnhi.cookingstips PID: 10091 java.lang.NullPointerExceptio... Users with phone manufactured by Lenovo might experience a crash on their phone!. Fix now!

Must fix: App crashed because of FATAL EXCEPTION: main Process: com.gamnhi.cookingstips PID: 10091 java.lang.NullPointerExceptio... Users with phone manufactured by Micromax might experience a crash on their phone!. Fix now!

Motorola Moto E (2nd gen) crashed at com.startsoft.cookingstips.activity.CategoriesActivity$3.onErrorResponse(CategoriesActivity.java:163) View details

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

Must fix: App crashed because of FATAL EXCEPTION: main Process: com.gamnhi.cookingstips PID: 10091 java.lang.NullPointerExceptio... 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.gamnhi.cookingstips PID: 10091 java.lang.NullPointerExceptio... Users with phone manufactured by Asus might experience a crash on their phone!. Fix now!

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.

Zenfone 2 Laser crashed at com.startsoft.cookingstips.activity.CategoriesActivity$3.onErrorResponse(CategoriesActivity.java:163) View details

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

Must fix: App crashed because of FATAL EXCEPTION: main Process: com.gamnhi.cookingstips PID: 10091 java.lang.NullPointerExceptio... Users with phone manufactured by LYF might experience a crash on their phone!. Fix now!

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

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

25 tests need immediate attention. View performance graph.

Utilization of Memory is close to the threshold.

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

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

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

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

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

65.07 MB of App Dalvik utilized by activity com.startsoft.cookingstips.activity.CategoriesActivity. View details

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

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

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

Caching: Use LruCache for data caching to optimize memory usage

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

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

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

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.

27 Tests crashed out of 27 Tests. Check where the app crashed. View details

Screen coverage

competition benchmark

This app is ranked #1592 in Books & Reference

1587
1588
1589
1590
1591
back-to-top