App Quality Dashboard

MapMyRide

1.2 / 5

Chhi Score

This app is performing

Poor

High Risk

/5

Medium Risk

/5

Good 

/5

Medium Risk

/5

#

 

Category

Rank

  • Install time: Icon 75.25 Sec
  • Launch time: Icon 2.70 Sec
  • Application size: Icon 87.90 MB
  • Last tested on : 18/05/2017
  • Build ID
    :   v17.5.0
  • Chhi Score
    :   1.2
  • Change Rate
    :   -50 %

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

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

Potential risk in Memory: Utilization has gone up by19.05% compared to build v17.3.1

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

4 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.

The app's CPU score has improved by 4.17% compared to build v17.3.1! Good job!

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

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

Utilization of CPU is close to the threshold.

9 tests need immediate attention. View performance graph.

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

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

Caching: Use LruCache for data caching to optimize memory usage

54.87 MB of App Dalvik utilized by activity com.mapmyfitness.android.activity.core.HostActivity. View details

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

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

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

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

Do not initialize objects that aren't necessary during launch times. Moving to singleton pattern helps

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

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

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

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

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

The app's Network score has improved by 2.78% compared to build v17.3.1! Good job!

Screen Coverage

competition benchmark

This app is ranked #1253 in Health & Fitness

1248
1249
1250
1251
1252
back-to-top