App Quality Dashboard

BigOven

3.9 / 5

Chhi Score

This app is performing

Average

Good

/5

Medium Risk

/5

Good 

/5

Good

/5

#

 

Category

Rank

  • Install time: Icon 44.38 Sec
  • Launch time: Icon 0.81 Sec
  • Application size: Icon 51.32 MB
  • Last tested on : 20/06/2017
  • Build ID
    :   v5.0.6
  • Chhi Score
    :   3.9
  • 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.

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

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

Build v5.6.17 did better in Network . Spikes in Network contributed to score drop by 8.16%

Utilization of CPU is close to the threshold.

3 tests need immediate attention. View performance graph.

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

The app's CPU score has improved by 7.14% compared to build v5.6.17! Good job!

Caching: Use LruCache for data caching to optimize memory usage

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

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

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

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

25.83 MB of App Dalvik utilized by activity com.facebook.FacebookActivity. View details

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

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

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

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

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

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

The app's Memory score has improved by 7.89% compared to build v5.6.17! Good job!

Screen Coverage

competition benchmark

This app is ranked #67 in Food & Drink

62
63
64
65
66
back-to-top