App Quality Dashboard

BellyFatBurning

1.5 / 5

Chhi Score

This app is performing

Poor

Medium Risk

/5

Medium Risk

/5

High  Risk

/5

Good

/5

#

 

Category

Rank

  • Install time: 4.17 Sec
  • Launch time: 0.78 Sec
  • Application size : 2.07 MB
  • Last tested on : 18/03/2017
  • Build ID
    :   v1.0
  • Chhi Score
    :   1.5
  • Change Rate
    :   0%

What to fix?

Must fix: App crashed because of FATAL EXCEPTION: main Process: com.educomapps.bellyfatburning PID: 23344 java.lang.RuntimeExcep... 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.educomapps.bellyfatburning PID: 23344 java.lang.RuntimeExcep... Users with phone manufactured by Motorola might experience a crash on their phone!. Fix now!

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

Motorola Moto E (2nd gen) crashed at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2426) View details

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.educomapps.bellyfatburning PID: 23344 java.lang.RuntimeExcep... Users with phone manufactured by YU might experience a crash on their phone!. Fix now!

Zenfone 2 Laser crashed at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2434) View details

Must fix: App crashed because of FATAL EXCEPTION: main Process: com.educomapps.bellyfatburning PID: 23344 java.lang.RuntimeExcep... 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.educomapps.bellyfatburning PID: 23344 java.lang.RuntimeExcep... 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.educomapps.bellyfatburning PID: 23344 java.lang.RuntimeExcep... 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.educomapps.bellyfatburning PID: 23344 java.lang.RuntimeExcep... Users with phone manufactured by Lenovo 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.

7 tests need immediate attention. View performance graph.

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

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

Utilization of Memory is close to the threshold.

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

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

46.08 MB of App Dalvik utilized by activity com.educomapps.bellyfatburning.MainActivity. View details

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

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

Caching: Use LruCache for data caching to optimize memory usage

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

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

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

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

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

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

13 Tests crashed out of 24 Tests. Check where the app crashed. 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

Screen coverage

competition benchmark

This app is ranked #1181 in Health & Fitness

1176
1177
1178
1179
1180
back-to-top