App Quality Dashboard

Android Wear

0.1 / 5

Chhi Score

This app is performing

Poor

Memory

CPU

High  Risk

/5

network

#

 

Category

Rank

  • Install time: 19.33 Sec
  • Launch time: 0.00 Sec
  • Application size : 26.08 MB
  • Last tested on : 16/06/2017
  • Build ID
    :   v1.5.0.2951640.gms
  • Chhi Score
    :   0.1
  • Change Rate
    :   0%

What to fix?

Oops!, The app crashed on Samsung Duos Galaxy J7, Lava Iris X8 & more devices. View details

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.

Lava Iris X8 crashed at android.os.Parcel.readException(Parcel.java:1465) View details

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 FATAL EXCEPTION: main Process: com.google.android.wearable.app PID: 11434 java.lang.SecurityExc... Users with phone manufactured by Lava might experience a crash on their phone!. Fix now!

Must fix: App crashed because of FATAL EXCEPTION: main Process: com.google.android.wearable.app PID: 11434 java.lang.SecurityExc... Users with phone manufactured by Samsung 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

Samsung Duos Galaxy J7 crashed at android.os.Parcel.readException(Parcel.java:1620) View details

Must fix: App crashed because of FATAL EXCEPTION: main Process: com.google.android.wearable.app PID: 11434 java.lang.SecurityExc... 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) Lava, LYF, Samsung. Check coverage report for more details.

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

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

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

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

Caching: Use LruCache for data caching to optimize memory usage

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

Do not initialize objects that aren't necessary during launch times. Moving to singleton pattern helps

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

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

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

98 apps having similar CPU load have low Chhi Scores

Avoid wake-locks in background, using Batch and schedulers APIs such as GCM, Job schedulers could reduce wake-locks

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

Fix Oncreate() if the launch time is exceeding more than 3.2 secs. Try deflating views and layouts to optimize.

competition benchmark

This app is ranked #638 in Communication

633
634
635
636
637
back-to-top