App Quality Dashboard

Baby Gender Predictor

0.9 / 5

Chhi Score

This app is performing

Poor

High Risk

/5

High Risk

/5

Good 

/5

Medium Risk

/5

#

 

Category

Rank

  • Install time: Icon 27.07 Sec
  • Launch time: Icon 3.00 Sec
  • Application size: Icon 7.43 MB
  • Last tested on : 28/03/2017
  • Build ID
    :   v2.4
  • Chhi Score
    :   0.9
  • Change Rate
    :   -18.18 %

What to fix?

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

Potential risk in Memory: Utilization has gone up by41.18% compared to build v2.2

Potential risk in CPU: Utilization has gone up by 44.44% compared to build v2.2

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.

Your App CPU 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

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

App launch time went up by 60.53% initlizate network calls after few seconds of loading the resources. View details

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

App size increased by 151.01% See how to optimize.

Consider re-merging the code from build v2.2, CPU score was 2.7

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

Consider re-merging the code from build v2.2, Memory score was 1.7

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

14 tests need immediate attention. View performance graph.

Build v2.2 did better in Network . Spikes in Network contributed to score drop by 19.57%

Utilization of CPU is close to the threshold.

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

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

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

Caching: Use LruCache for data caching to optimize memory usage

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

124.00 MB of App Dalvik utilized by activity net.pregencttest.www.MainActivity. View details

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.

508 apps having similar CPU load have low Chhi Scores

Your average App Dalvik usage surged by 35.7%, Your memory score is 1.0

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

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.

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

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

Screen Coverage

competition benchmark

This app is ranked #2318 in Entertainment

2313
2314
2315
2316
2317
back-to-top