App Quality Dashboard

FitWell

3.6 / 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 41.19 Sec
  • Launch time: Icon 5.00 Sec
  • Application size: Icon 38.00 MB
  • Last tested on : 06/05/2017
  • Build ID
    :   v2.10.4
  • Chhi Score
    :   3.6
  • Change Rate
    :   -2.7 %

Insights (26)

What to fix?

Build v2.10.2 did better in Memory . Spikes in Memory contributed to score drop by 5.41%
Build v2.10.2 did better in CPU . Spikes in CPU contributed to score drop by 25%
App launch time went up by INF% initlizate network calls after few seconds of loading the resources. View details
2 Risk(s) are due to Threads in CPU exceeding the threshold.
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.10.2 did better in Network . Spikes in Network contributed to score drop by 6.25%
Utilization of CPU is close to the threshold.
8 tests need immediate attention. View performance graph.
The app has a high performance risk for the phone manufacturer(s) Panasonic, Lenovo, Motorola, LYF, Asus. Check coverage report for more details.
Consider re-merging the code from build v2.10.2, CPU score was 3.6
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
Optimize the app to render elements at 60 FPS for buttery smooth experience.
79.64 MB of App Dalvik utilized by activity tr.com.fitwell.app.activities.ActivityLogin. View details
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.
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 & Optimize launch time using Flatbuffers for storage and rendering performance.
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.
Your average App Dalvik usage surged by 43.11%, Your memory score is 3.5
There is high probability of identifying risks running the apps with conditions
Below 10 MB approach would increase app installs in crowded markets such as India, China and Russia!
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
Unlock more fixes

Screen Coverage

competition benchmark

This app is ranked #343 in Health & Fitness

338
339
340
341
342
back-to-top