App Quality Dashboard

BlackBerry Launcher

1.1 / 5

Chhi Score

This app is performing

Poor

Memory

Good

/5

CPU

Medium Risk

/5

crash

High  Risk

/5

network

Good

/5

Competition

#

 

Category

Rank

  • Install time: Icon 46.10 Sec
  • Launch time: Icon 0.95 Sec
  • Application size: Icon 52.25 MB
  • Last tested on : 03/04/2017
  • Build ID
    :   v1.1.2.6522
  • Chhi Score
    :   1.1
  • Change Rate
    :   +10 %

Insights (30)

What to fix?

App launch time went up by 18.75% initlizate network calls after few seconds of loading the resources. View details
Must fix: App crashed because of 734): FATAL EXCEPTION: main 734): Process: com.blackberry.blackberrylauncher PID: 734 734): j... Users with phone manufactured by Lenovo might experience a crash on their phone!. Fix now!
Must fix: App crashed because of 734): FATAL EXCEPTION: main 734): Process: com.blackberry.blackberrylauncher PID: 734 734): j... Users with phone manufactured by Karbonn might experience a crash on their phone!. Fix now!
Must fix: App crashed because of 734): FATAL EXCEPTION: main 734): Process: com.blackberry.blackberrylauncher PID: 734 734): j... Users with phone manufactured by Panasonic might experience a crash on their phone!. Fix now!
Must fix: App crashed because of 734): FATAL EXCEPTION: main 734): Process: com.blackberry.blackberrylauncher PID: 734 734): j... Users with phone manufactured by Micromax might experience a crash on their phone!. Fix now!
Karbonn Titanium Machfive crashed at com.blackberry.blackberrylauncher.HomeIconActivity$a.onDismiss(SourceFile:119) View details
Oops!, The app crashed on Lenovo A6000, Karbonn Titanium Machfive & more devices. View details
Must fix: App crashed because of 734): FATAL EXCEPTION: main 734): Process: com.blackberry.blackberrylauncher PID: 734 734): j... Users with phone manufactured by YU might experience a crash on their phone!. Fix now!
Lenovo A6000 crashed at com.blackberry.blackberrylauncher.HomeIconActivity$a.onDismiss(SourceFile:119) View details
Must fix: App crashed because of 734): FATAL EXCEPTION: main 734): Process: com.blackberry.blackberrylauncher PID: 734 734): j... Users with phone manufactured by Samsung might experience a crash on their phone!. Fix now!
Must fix: App crashed because of 734): FATAL EXCEPTION: main 734): Process: com.blackberry.blackberrylauncher PID: 734 734): j... Users with phone manufactured by LYF might experience a crash on their phone!. Fix now!
Must fix: App crashed because of 734): FATAL EXCEPTION: main 734): Process: com.blackberry.blackberrylauncher PID: 734 734): j... Users with phone manufactured by Lenovo might experience a crash on their phone!. Fix now!
Build v1.1.2.6350 did better in CPU . Spikes in CPU contributed to score drop by 11.36%
The app has a high performance risk for the phone manufacturer(s) LYF, Karbonn, Panasonic, Lenovo, YU, Micromax, Samsung. Check coverage report for more details.
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.
10 Tests crashed out of 10 Tests. Check where the app crashed. View details
Coverage: Android version coverage for reports will range between 5.1.1 to 7.1.2
26.45 MB of App Dalvik utilized by activity com.blackberry.blackberrylauncher.HomeIconActivity. View details
Upload APKs with and without 3rd Party SDKs to monitor and optimize the impact of app performance
Testability: Providing login / sign-up details could very well improve depth of bot clicks
There is high probability of identifying risks running the apps with conditions
Printing logs on callbacks would make debugging easy for tests run in our platform
Optimize the app to render elements at 60 FPS for buttery smooth experience.
Fix Oncreate() if the launch time is exceeding more than 3.2 secs. Try deflating views and layouts to optimize.
Do not initialize objects that aren't necessary during launch times. Moving to singleton pattern helps
Follow simple UI hierarchy by reducing nested layouts to Relative layouts.
Caching: Use LruCache for data caching to optimize memory usage
Avoid wake-locks in background, using Batch and schedulers APIs such as GCM, Job schedulers could reduce wake-locks
The app's Memory score has improved by 2.27% compared to build v1.1.2.6350! Good job!
Unlock more fixes

Screen Coverage

competition benchmark

This app is ranked #1041 in Productivity

1036
1037
1038
1039
1040
back-to-top