App Quality Dashboard

Paktor

3.6 / 5

Chhi Score

This app is performing

Average

Memory

Medium Risk

/5

CPU

Medium Risk

/5

crash

Medium  Risk

/5

network

Good

/5

Competition

#

 

Category

Rank

  • Install time: Icon 25.05 Sec
  • Launch time: Icon 1.14 Sec
  • Application size: Icon 23.69 MB
  • Last tested on : 22/05/2017
  • Build ID
    :   v2.9.4
  • Chhi Score
    :   3.6
  • Change Rate
    :   +2.86 %

Insights (30)

What to fix?

Must fix: App crashed because of FATAL EXCEPTION: main Process: com.paktor PID: 17474 java.lang.RuntimeException: Failure delive... Users with phone manufactured by Lenovo might experience a crash on their phone!. Fix now!
Must fix: App crashed because of FATAL EXCEPTION: main Process: com.paktor PID: 17474 java.lang.RuntimeException: Failure delive... Users with phone manufactured by Asus might experience a crash on their phone!. Fix now!
7 Risk(s) are due to Threads in CPU exceeding the threshold.
Must fix: App crashed because of FATAL EXCEPTION: main Process: com.paktor PID: 17474 java.lang.RuntimeException: Failure delive... Users with phone manufactured by Karbonn might experience a crash on their phone!. Fix now!
Must fix: App crashed because of FATAL EXCEPTION: main Process: com.paktor PID: 17474 java.lang.RuntimeException: Failure delive... Users with phone manufactured by Panasonic might experience a crash on their phone!. Fix now!
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.
Fixing CPU risks could drastically improve Chhi Score. There are 7 CPU risks.
Must fix: App crashed because of FATAL EXCEPTION: main Process: com.paktor PID: 17474 java.lang.RuntimeException: Failure delive... Users with phone manufactured by LYF might experience a crash on their phone!. Fix now!
The app has a high performance risk for the phone manufacturer(s) Karbonn, LYF, Panasonic, Lenovo, Asus. Check coverage report for more details.
7 tests need immediate attention. View performance graph.
Utilization of CPU is close to the threshold.
Coverage: Android version coverage for reports will range between 5.1.1 to 7.1.2
Do not initialize objects that aren't necessary during launch times. Moving to singleton pattern helps
Upload APKs with and without 3rd Party SDKs to monitor and optimize the impact of app performance
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.
Caching: Use LruCache for data caching to optimize memory usage
Testability: Providing login / sign-up details could very well improve depth of bot clicks
Printing logs on callbacks would make debugging easy for tests run in our platform
Fix Oncreate() if the launch time is exceeding more than 3.2 secs. Try deflating views and layouts to optimize.
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
Fix & Optimize launch time using Flatbuffers for storage and rendering performance.
The app has crashed on few device(s)! View details
Follow simple UI hierarchy by reducing nested layouts to Relative layouts.
5 Tests crashed out of 21 Tests. Check where the app crashed. View details
65.45 MB of App Dalvik utilized by activity com.facebook.accountkit.ui.AccountKitActivity. View details
The app's Memory score has improved by 5.26% compared to build v2.9.2! Good job!
Well done, Network consumption has come down by 97.56 % compared to build v2.9.2
The app's Network score has improved by 11.11% compared to build v2.9.2! Good job!
Unlock more fixes

Screen Coverage

competition benchmark

This app is ranked #836 in Lifestyle

831
832
833
834
835
back-to-top