App Quality Dashboard

HipBar

2.2 / 5

Chhi Score

This app is performing

Average

Medium Risk

/5

Medium Risk

/5

Good 

/5

High Risk

/5

#

 

Category

Rank

  • Install time: Icon 16.95 Sec
  • Launch time: Icon 0.62 Sec
  • Application size: Icon 6.45 MB
  • Last tested on : 12/05/2017
  • Build ID
    :   v0.1.3
  • Chhi Score
    :   2.2
  • Change Rate
    :   -40.54 %

What to fix?

Build v0.0.8 did better in CPU . Spikes in CPU contributed to score drop by 11.76%

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

Potential risk in Network: Utilization has gone up by76% compared to build v0.0.8

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

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 v0.0.8 did better in Memory . Spikes in Memory contributed to score drop by 5.41%

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

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

Utilization of CPU is close to the threshold.

App size increased by 22.39% See how to optimize.

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

7 tests need immediate attention. View performance graph.

Consider re-merging the code from build v0.0.8, Network score was 5.0

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

Your average App Dalvik usage surged by 8.85%, Your memory score is 3.5

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

85.39 MB of App Dalvik utilized by activity in.hipbar.hipbar_user_app.UI.Activity.IntroActivity. View details

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

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

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

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

App makes 3295.57 KB of network requests. Moving this to a background thread will improve load speed. View 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

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

Total Network data consumed was 3295.57KB 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

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

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

Network utilization on Zenfone 2 Laser exceeded 1024 KB, you might want to consider bringing it down

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

Screen coverage

competition benchmark

This app is ranked #308 in Food & Drink

303
304
305
306
307
back-to-top