App Quality Dashboard

BE

1.0 / 5

Chhi Score

This app is performing

Poor

High Risk

/5

Medium Risk

/5

Good 

/5

Good

/5

#

 

Category

Rank

  • Install time: 36.43 Sec
  • Launch time: 5.00 Sec
  • Application size : 51.47 MB
  • Last tested on : 01/05/2017
  • Build ID
    :   v1.0.2
  • Chhi Score
    :   1.0
  • Change Rate
    :   0%

What to fix?

Your App Memory is now in a High Risk Zone. With a small investment into your testing you can improve your app quality better. Get more test coverage

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

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

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.

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

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

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

Utilization of CPU is close to the threshold.

21 tests need immediate attention. View performance graph.

3 Risk(s) are due to CPU Load in CPU exceeding the threshold.

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

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 & Optimize launch time using Flatbuffers for storage and rendering performance.

33.00 MB of App Dalvik utilized by activity air.com.kigorosa.babyentwicklung.ad.AppEntry. View details

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

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

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

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

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

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

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

Screen Coverage

competition benchmark

This app is ranked #652 in Medical

647
648
649
650
651
back-to-top