App Quality Dashboard

CalorieMama

3.8 / 5

Chhi Score

This app is performing

Average

Memory

Medium Risk

/5

CPU

Medium Risk

/5

crash

Good 

/5

network

Good

/5

Competition

#

 

Category

Rank

  • Install time: Icon 45.36 Sec
  • Launch time: Icon 1.90 Sec
  • Application size: Icon 35.93 MB
  • Last tested on : 14/05/2017
  • Build ID
    :   v5.36.3234
  • Chhi Score
    :   3.8
  • Change Rate
    :   -7.32 %

Insights (26)

What to fix?

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.
App launch time went up by INF% initlizate network calls after few seconds of loading the resources. View details
6 Risk(s) are due to Threads in CPU exceeding the threshold.
Build v5.36.3187 did better in CPU . Spikes in CPU contributed to score drop by 39.02%
Fixing CPU risks could drastically improve Chhi Score. There are 6 CPU risks.
Consider re-merging the code from build v5.36.3187, CPU score was 4.1
App size increased by 29.06% See how to optimize.
Build v5.36.3187 did better in Memory . Spikes in Memory contributed to score drop by 12.2%
The app has a high performance risk for the phone manufacturer(s) Motorola, Panasonic, Lenovo. Check coverage report for more details.
9 tests need immediate attention. View performance graph.
Utilization of CPU is close to the threshold.
Coverage: Android version coverage for reports will range between 5.1.1 to 7.1.2
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!
76.82 MB of App Dalvik utilized by activity com.azumio.android.argus.authentication.AuthenticationActivity. View details
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
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
Follow simple UI hierarchy by reducing nested layouts to Relative layouts.
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.
There is high probability of identifying risks running the apps with conditions
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
Well done, Network consumption has come down by 86.64 % compared to build v5.36.3187
Unlock more fixes

Screen Coverage

competition benchmark

This app is ranked #311 in Health & Fitness

306
307
308
309
310
back-to-top