App Quality Dashboard

Healofy

3.9 / 5

Chhi Score

This app is performing

Average

Good

/5

Medium Risk

/5

Good 

/5

Good

/5

#

 

Category

Rank

  • Install time: Icon 10.75 Sec
  • Launch time: Icon 1.33 Sec
  • Application size: Icon 4.94 MB
  • Last tested on : 30/05/2017
  • Build ID
    :   v2.0.23
  • Chhi Score
    :   3.9
  • Change Rate
    :   -7.14 %

What to fix?

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

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.

Build v2.0.21 did better in CPU . Spikes in CPU contributed to score drop by 19.51%

Utilization of CPU is close to the threshold.

Consider re-merging the code from build v2.0.21, CPU score was 4.1

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

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

Caching: Use LruCache for data caching to optimize memory usage

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

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

52.25 MB of App Dalvik utilized by activity com.vivoiz.healofy.patient.Activity.UserTypeActivity. View details

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

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

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

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

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

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

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

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

The app's Memory score has improved by 2.38% compared to build v2.0.21! Good job!

competition benchmark

This app is ranked #21 in Parenting

16
17
18
19
20
back-to-top