App Quality Dashboard

Simply Crochet

1.9 / 5

Chhi Score

This app is performing

Average

Medium Risk

/5

Medium Risk

/5

Medium  Risk

/5

High Risk

/5

#

 

Category

Rank

  • Install time: 17.00 Sec
  • Launch time: 0.83 Sec
  • Application size : 10.60 MB
  • Last tested on : 13/05/2017
  • Build ID
    :   v5.3.6
  • Chhi Score
    :   1.9
  • Change Rate
    :   0%

What to fix?

9 Risk(s) are due to Data Sent/Received in Network exceeding the threshold.

Must fix: App crashed because of FATAL EXCEPTION: Thread-680 Process: com.im.simplycrochet PID: 17326 java.util.ConcurrentModifi... Users with phone manufactured by Lenovo might experience a crash on their phone!. Fix now!

Motorola Moto E (2nd gen) crashed attached to Activity at android.support.v4.app.Fragment.getResources(Fragment.java:651) View details

Must fix: App crashed because of FATAL EXCEPTION: Thread-680 Process: com.im.simplycrochet PID: 17326 java.util.ConcurrentModifi... Users with phone manufactured by Panasonic might experience a crash on their phone!. Fix now!

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

Must fix: App crashed because of FATAL EXCEPTION: Thread-680 Process: com.im.simplycrochet PID: 17326 java.util.ConcurrentModifi... Users with phone manufactured by Lava might experience a crash on their phone!. Fix now!

Must fix: App crashed because of FATAL EXCEPTION: Thread-680 Process: com.im.simplycrochet PID: 17326 java.util.ConcurrentModifi... Users with phone manufactured by Motorola might experience a crash on their phone!. Fix now!

Must fix: App crashed because of FATAL EXCEPTION: Thread-680 Process: com.im.simplycrochet PID: 17326 java.util.ConcurrentModifi... Users with phone manufactured by LYF might experience a crash on their phone!. Fix now!

Must fix: App crashed because of FATAL EXCEPTION: Thread-680 Process: com.im.simplycrochet PID: 17326 java.util.ConcurrentModifi... Users with phone manufactured by Asus might experience a crash on their phone!. Fix now!

Fixing Network risks could drastically improve Chhi Score. There are 9 Network risks.

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

9 Risk(s) are due to App PSS in Memory exceeding the threshold. See how to optimize memory and remove 9 High Risk(s).

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.

Lenovo A6000 crashed attached to Activity at android.support.v4.app.Fragment.getResources(Fragment.java:651) View details

Oops!, The app crashed on Lenovo A6000, Motorola Moto E (2nd gen) & more devices. View details

Must fix: App crashed because of FATAL EXCEPTION: Thread-680 Process: com.im.simplycrochet PID: 17326 java.util.ConcurrentModifi... Users with phone manufactured by YU might experience a crash on their phone!. Fix now!

Utilization of Memory is close to the threshold.

2 Risk(s) are due to App Total in Memory exceeding the threshold.

17 tests need immediate attention. View performance graph.

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

Utilization of CPU is close to the threshold.

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

9 Tests crashed out of 30 Tests. Check where the app crashed. View details

119.04 MB of App Dalvik utilized by activity com.immediate.imcreader.MainActivity. View details

Network utilization on Lenovo A6000 exceeded 1024 KB, you might want to consider bringing it down

Testability: Providing login / sign-up details could very well improve depth of bot clicks

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

App makes 12771.60 KB of network requests. Moving this to a background thread will improve load speed. View details

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

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

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

Network utilization on Motorola Moto E (2nd gen) exceeded 1024 KB, you might want to consider bringing it down

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!

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

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

Total Network data consumed was 12771.60KB in Motorola Moto E (2nd gen) , This indicates the app will take 10-15 seconds on 2G network and 8-9 seconds on 3G network to load! View details

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

Screen coverage

competition benchmark

This app is ranked #979 in News & Magazines

974
975
976
977
978
back-to-top