App Quality Dashboard

hi5

2.8 / 5

Chhi Score

This app is performing

Average

Medium Risk

/5

Medium Risk

/5

Good 

/5

Good

/5

#

 

Category

Rank

  • Install time: Icon 47.65 Sec
  • Launch time: Icon 4.00 Sec
  • Application size: Icon 39.72 MB
  • Last tested on : 19/04/2017
  • Build ID
    :   v7.2
  • Chhi Score
    :   2.8
  • Change Rate
    :   -15.15 %

What to fix?

Build v7.0 did better in CPU . Spikes in CPU contributed to score drop by 21.43%

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

10 Risk(s) are due to App PSS in Memory exceeding the threshold. See how to optimize memory and remove 10 High Risk(s).

Fixing CPU risks could drastically improve Chhi Score. There are 14 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.

Build v7.0 did better in Memory . Spikes in Memory contributed to score drop by 19.35%

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

The app took 4.00 seconds to load on Android OS version 5.0.2. Usually anything more than 3.2 seconds results in user drops. View details

Consider re-merging the code from build v7.0, Memory score was 3.1

Utilization of Memory is close to the threshold.

The app has a high performance risk for the phone manufacturer(s) Lenovo, Samsung, Motorola, Spice, YU, Lava, Panasonic, Micromax. Check coverage report for more details.

Consider re-merging the code from build v7.0, CPU score was 2.8

3 Risk(s) are due to App Total in Memory exceeding the threshold.

Utilization of CPU is close to the threshold.

16 tests need immediate attention. View performance graph.

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

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

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

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

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

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

Caching: Use LruCache for data caching to optimize memory usage

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

43.26 MB of App Dalvik utilized by activity com.tagged.activity.AuthenticationActivity. View details

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

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

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

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

Well done, Network consumption has come down by 55.58 % compared to build v7.0

The app's Network score has improved by 6.67% compared to build v7.0! Good job!

Screen coverage

Test Flows YU Yuphoria Spice Mi-498 Dream Uno Lava Iris X8 Panasonic P55 Micromax Canvas AQ4502 Lenovo VIBE K4 Note Samsung Galaxy J7 Motorola Moto E (2nd gen)

Install app

  • Risk

  • Risk

  • Risk

  • Risk

  • Risk

  • Risk

  • Success

  • Risk

Scenario 1

  • Risk

  • Risk

  • Risk

  • Risk

  • Risk

  • Risk

  • Risk

  • Risk

Scenario 2

  • Risk

competition benchmark

This app is ranked #509 in Social

504
505
506
507
508
back-to-top