App Quality Dashboard

SMS Collection

0.1 / 5

Chhi Score

This app is performing

Poor

Memory

CPU

crash

High  Risk

/5

network

Competition

#

 

Category

Rank

  • Install time: 2.89 Sec
  • Launch time: 0.00 Sec
  • Application size : 1.53 MB
  • Last tested on : 08/02/2017
  • Build ID
    :   2.7
  • Chhi Score
    :   0.1
  • Change Rate
    :   0%

Insights (31)

What to fix?

Motorola Nexus 6 crashed at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2646) View details
Must fix: App crashed because of 5110): FATAL EXCEPTION: main 5110): Process: com.atomic.apps.sms.messages.collections PID: 5110... Users with phone manufactured by Lenovo might experience a crash on their phone!. Fix now!
Must fix: App crashed because of 5110): FATAL EXCEPTION: main 5110): Process: com.atomic.apps.sms.messages.collections PID: 5110... Users with phone manufactured by Asus might experience a crash on their phone!. Fix now!
Your App CPU is now in a High Risk Zone. With a small investment into your testing you can improve your app quality better. Get more test coverage
Must fix: App crashed because of 5110): FATAL EXCEPTION: main 5110): Process: com.atomic.apps.sms.messages.collections PID: 5110... Users with phone manufactured by OnePlus might experience a crash on their phone!. Fix now!
Must fix: App crashed because of 5110): FATAL EXCEPTION: main 5110): Process: com.atomic.apps.sms.messages.collections PID: 5110... Users with phone manufactured by Motorola might experience a crash on their phone!. Fix now!
Must fix: App crashed because of 5110): FATAL EXCEPTION: main 5110): Process: com.atomic.apps.sms.messages.collections PID: 5110... Users with phone manufactured by vivo might experience a crash on their phone!. Fix now!
Your App Memory is now in a High Risk Zone. With a small investment into your testing you can improve your app quality better. Get more test coverage
Must fix: App crashed because of 5110): FATAL EXCEPTION: main 5110): Process: com.atomic.apps.sms.messages.collections PID: 5110... Users with phone manufactured by Motorola might experience a crash on their phone!. Fix now!
Oops!, The app crashed on Motorola Nexus 6, Motorola Moto G 2014 XT1068 Dual 8GB & more devices. View details
Motorola Moto G 2014 XT1068 Dual 8GB crashed at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2426) View details
Must fix: App crashed because of 5110): FATAL EXCEPTION: main 5110): Process: com.atomic.apps.sms.messages.collections PID: 5110... Users with phone manufactured by Lenovo might experience a crash on their phone!. Fix now!
Must fix: App crashed because of 5110): FATAL EXCEPTION: main 5110): Process: com.atomic.apps.sms.messages.collections PID: 5110... Users with phone manufactured by Karbonn might experience a crash on their phone!. Fix now!
Must fix: App crashed because of 5110): FATAL EXCEPTION: main 5110): Process: com.atomic.apps.sms.messages.collections PID: 5110... Users with phone manufactured by Coolpad 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.
The app has a high performance risk for the phone manufacturer(s) OnePlus, Asus, Motorola, vivo, Karbonn, Coolpad, Lenovo. Check coverage report for more details.
Optimize the app to render elements at 60 FPS for buttery smooth experience.
Coverage: Android version coverage for reports will range between 5.1.1 to 7.1.2
Below 10 MB approach would increase app installs in crowded markets such as India, China and Russia!
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
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
Avoid wake-locks in background, using Batch and schedulers APIs such as GCM, Job schedulers could reduce wake-locks
Printing logs on callbacks would make debugging easy for tests run in our platform
27 Tests crashed out of 27 Tests. Check where the app crashed. View details
98 apps having similar CPU load have low Chhi Scores
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.
Follow simple UI hierarchy by reducing nested layouts to Relative layouts.
Caching: Use LruCache for data caching to optimize memory usage
Unlock more fixes
competition benchmark

This app is ranked #626 in Communication

621
622
623
624
625
back-to-top