App Quality Dashboard

Friday

1.0 / 5

Chhi Score

This app is performing

Poor

High Risk

/5

Medium Risk

/5

Good 

/5

High Risk

/5

#

 

Category

Rank

  • Install time: 10.07 Sec
  • Launch time: 3.02 Sec
  • Application size : 4.47 MB
  • Last tested on : 31/03/2017
  • Build ID
    :   v1.1
  • Chhi Score
    :   1.0
  • Change Rate
    :   0%

What to fix?

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

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

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

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

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

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

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

Utilization of Memory is close to the threshold.

Utilization of CPU is close to the threshold.

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

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

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.

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

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

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

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

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

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

Total Network data consumed was 5101.54KB in Lenovo A6000 , This indicates the app will take 10-15 seconds on 2G network and 8-9 seconds on 3G network to load! View details

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

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

65.75 MB of App Dalvik utilized by activity ch.edge5.nativeMenuFridayMagazineFr.nativeMenuFridayMagazine.activity.MainActivity. View details

Caching: Use LruCache for data caching to optimize memory usage

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

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

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

Screen coverage

competition benchmark

This app is ranked #3333 in Lifestyle

3328
3329
3330
3331
3332
back-to-top