App Quality Dashboard

Get Pregnant

1.2 / 5

Chhi Score

This app is performing

Poor

Medium Risk

/5

Medium Risk

/5

High  Risk

/5

Good

/5

#

 

Category

Rank

  • Install time: 11.00 Sec
  • Launch time: 5.00 Sec
  • Application size : 7.52 MB
  • Last tested on : 24/05/2017
  • Build ID
    :   v2.0
  • Chhi Score
    :   1.2
  • Change Rate
    :   0%

What to fix?

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

Must fix: App crashed because of FATAL EXCEPTION: main Process: get.pregnant.fertility PID: 13432 java.lang.RuntimeException: ... Users with phone manufactured by OnePlus might experience a crash on their phone!. Fix now!

Must fix: App crashed because of FATAL EXCEPTION: main Process: get.pregnant.fertility PID: 13432 java.lang.RuntimeException: ... Users with phone manufactured by YU might experience a crash on their phone!. Fix now!

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

Must fix: App crashed because of FATAL EXCEPTION: main Process: get.pregnant.fertility PID: 13432 java.lang.RuntimeException: ... Users with phone manufactured by Spice might experience a crash on their phone!. Fix now!

Must fix: App crashed because of FATAL EXCEPTION: main Process: get.pregnant.fertility PID: 13432 java.lang.RuntimeException: ... Users with phone manufactured by Panasonic 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.

Must fix: App crashed because of FATAL EXCEPTION: main Process: get.pregnant.fertility PID: 13432 java.lang.RuntimeException: ... Users with phone manufactured by Karbonn might experience a crash on their phone!. Fix now!

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

Must fix: App crashed because of FATAL EXCEPTION: main Process: get.pregnant.fertility PID: 13432 java.lang.RuntimeException: ... 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: get.pregnant.fertility PID: 13432 java.lang.RuntimeException: ... Users with phone manufactured by Motorola might experience a crash on their phone!. Fix now!

Motorola Moto G 2014 XT1068 Dual 8GB crashed at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2426) View details

Must fix: App crashed because of FATAL EXCEPTION: main Process: get.pregnant.fertility PID: 13432 java.lang.RuntimeException: ... 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: get.pregnant.fertility PID: 13432 java.lang.RuntimeException: ... Users with phone manufactured by Motorola might experience a crash on their phone!. Fix now!

Oops!, The app crashed on Motorola Moto E (2nd gen), Motorola Moto G 2014 XT1068 Dual 8GB & more devices. View details

Utilization of CPU is close to the threshold.

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

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

27 tests need immediate attention. View performance graph.

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

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

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

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

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

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

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

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

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

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

Caching: Use LruCache for data caching to optimize memory usage

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

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

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

Screen Coverage

competition benchmark

This app is ranked #1255 in Health & Fitness

1250
1251
1252
1253
1254
back-to-top