App Quality Dashboard

MapMyHike

1.3 / 5

Chhi Score

This app is performing

Poor

Medium Risk

/5

High Risk

/5

Good 

/5

Medium Risk

/5

#

 

Category

Rank

  • Install time: Icon 88.00 Sec
  • Launch time: Icon 1.41 Sec
  • Application size: Icon 88.32 MB
  • Last tested on : 17/05/2017
  • Build ID
    :   v17.4.1
  • Chhi Score
    :   1.3
  • Change Rate
    :   -43.48 %

What to fix?

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

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

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

Build v17.3.1 did better in Memory . Spikes in Memory contributed to score drop by 5%

Potential risk in CPU: Utilization has gone up by 26.09% compared to build v17.3.1

3 tests need immediate attention. View performance graph.

Build v17.3.1 did better in Network . Spikes in Network contributed to score drop by 2.7%

Consider re-merging the code from build v17.3.1, CPU score was 2.3

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

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

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

Caching: Use LruCache for data caching to optimize memory usage

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

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!

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

254 apps having similar CPU load have low Chhi Scores

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

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

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

71.20 MB of App Dalvik utilized by activity com.facebook.FacebookActivity. View details

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

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

Your average App Dalvik usage surged by 34.84%, Your memory score is 1.9

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

Screen Coverage

competition benchmark

This app is ranked #1224 in Health & Fitness

1219
1220
1221
1222
1223
back-to-top