App Quality Dashboard

F8

2.3 / 5

Chhi Score

This app is performing

Average

Medium Risk

/5

Medium Risk

/5

Good 

/5

Medium Risk

/5

#

 

Category

Rank

  • Install time: Icon 14.95 Sec
  • Launch time: Icon 0.69 Sec
  • Application size: Icon 10.95 MB
  • Last tested on : 18/04/2017
  • Build ID
    :   v4.0.0
  • Chhi Score
    :   2.3
  • Change Rate
    :   -25.81 %

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.

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

Fixing CPU risks could drastically improve Chhi Score. There are 8 CPU risks.

Build v3.2.3 did better in CPU . Spikes in CPU contributed to score drop by 3.33%

Build v3.2.3 did better in Memory . Spikes in Memory contributed to score drop by 27.59%

1 Risk(s) are due to CPU Load in CPU exceeding the threshold.

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

19 tests need immediate attention. View performance graph.

Build v3.2.3 did better in Network . Spikes in Network contributed to score drop by 19.15%

Utilization of CPU is close to the threshold.

Consider re-merging the code from build v3.2.3, Memory score was 2.9

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

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

54.41 MB of App Dalvik utilized by activity com.facebook.f8.MainActivity. View details

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

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

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

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

Your average App Dalvik usage surged by 53.2%, Your memory score is 2.1

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.

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.

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

Screen Coverage

competition benchmark

This app is ranked #1037 in Business

1032
1033
1034
1035
1036
back-to-top