App Quality Dashboard

Give Me 5

1.0 / 5

Chhi Score

This app is performing

Poor

High Risk

/5

Medium Risk

/5

Good 

/5

Good

/5

#

 

Category

Rank

  • Install time: 22.07 Sec
  • Launch time: 4.00 Sec
  • Application size : 23.09 MB
  • Last tested on : 22/04/2017
  • Build ID
    :   v1.0.2
  • Chhi Score
    :   1.0
  • Change Rate
    :   0%

What to fix?

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

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

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

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

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

Utilization of CPU is close to the threshold.

7 tests need immediate attention. View performance graph.

Make sure your App's PSS isn't too high. Freeing objects that aren't needed would reduce chances of getting unexpectedly killed by Android system.

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

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

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

Caching: Use LruCache for data caching to optimize memory usage

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

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

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

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

33.97 MB of App Dalvik utilized by activity com.groupebayard.giveme5.MainActivity. View details

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.

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

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

Screen coverage

competition benchmark

This app is ranked #1306 in News & Magazines

1301
1302
1303
1304
1305
back-to-top