App Quality Dashboard

Plurk

1.0 / 5

Chhi Score

This app is performing

Poor

Medium Risk

/5

Medium Risk

/5

High  Risk

/5

Good

/5

#

 

Category

Rank

  • Install time: Icon 18.00 Sec
  • Launch time: Icon 0.47 Sec
  • Application size: Icon 8.39 MB
  • Last tested on : 19/05/2017
  • Build ID
    :   v4.5.8
  • Chhi Score
    :   1.0
  • Change Rate
    :   -50 %

What to fix?

Must fix: App crashed because of FATAL EXCEPTION: main Process: com.plurk.android PID: 18429 java.lang.RuntimeException: Unable ... Users with phone manufactured by Karbonn might experience a crash on their phone!. Fix now!

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

Build v4.5.5 did better in CPU . Spikes in CPU contributed to score drop by 17.86%

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

Must fix: App crashed because of FATAL EXCEPTION: main Process: com.plurk.android PID: 18429 java.lang.RuntimeException: Unable ... Users with phone manufactured by Lenovo might experience a crash on their phone!. Fix now!

3 tests need immediate attention. View performance graph.

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

Consider re-merging the code from build v4.5.5, CPU score was 2.8

4 Tests crashed out of 6 Tests. Check where the app crashed. View details

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

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

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

67.72 MB of App Dalvik utilized by activity com.plurk.android.start.NewStart. View details

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

The app has crashed on few device(s)! View details

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

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

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

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.

Caching: Use LruCache for data caching to optimize memory usage

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

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

Well done, Network consumption has come down by 40.58 % compared to build v4.5.5

The app's Network score has improved by 2.04% compared to build v4.5.5! Good job!

Screen Coverage

competition benchmark

This app is ranked #739 in Social

734
735
736
737
738
back-to-top