App Quality Dashboard

HERE WeGo

0.6 / 5

Chhi Score

This app is performing

Poor

High Risk

/5

High Risk

/5

Good 

/5

High Risk

/5

#

 

Category

Rank

  • Install time: Icon 51.57 Sec
  • Launch time: Icon 0.40 Sec
  • Application size: Icon 40.01 MB
  • Last tested on : 25/03/2017
  • Build ID
    :   v2.0.11360
  • Chhi Score
    :   0.6
  • Change Rate
    :   +20 %

What to fix?

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

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

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

15 Risk(s) are due to Data Sent/Received in Network exceeding the threshold.

Fixing Network risks could drastically improve Chhi Score. There are 15 Network risks.

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

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.

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

20 tests need immediate attention. View performance graph.

The app'sMemory score has improved by30%!

The app has a high performance risk for the phone manufacturer(s) Asus, Karbonn, Motorola, Lava, LYF, Lenovo, Panasonic. Check coverage report for more details.

Utilization of CPU is close to the threshold.

Utilization of Network is close to the threshold.

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

Caching: Use LruCache for data caching to optimize memory usage

120 apps having similar CPU load have low Chhi Scores

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

33.05 MB of App Dalvik utilized by activity com.here.app.ftu.activities.FtuActivity. View details

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

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

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

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

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

Network utilization on Lenovo A6000 exceeded 1024 KB, you might want to consider bringing it down

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

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

Total Network data consumed was 6270.34KB in Motorola Moto E (2nd gen) , This indicates the app will take 10-15 seconds on 2G network and 8-9 seconds on 3G network to load! View details

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

App makes 6270.34 KB of network requests. Moving this to a background thread will improve load speed. View details

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

Network utilization on Motorola Moto E (2nd gen) exceeded 1024 KB, you might want to consider bringing it down

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

Well done, Network consumption has come down by 31.75 % compared to build v2.0.11304

competition benchmark

This app is ranked #492 in Maps & Navigation

487
488
489
490
491
back-to-top