App Quality Dashboard

WRICN

0.1 / 5

Chhi Score

This app is performing

Poor

Memory

CPU

High  Risk

/5

network

#

 

Category

Rank

  • Install time: 4.33 Sec
  • Launch time: 0.00 Sec
  • Application size : 2.02 MB
  • Last tested on : 11/03/2017
  • Build ID
    :   v2.3.2
  • Chhi Score
    :   0.1
  • Change Rate
    :   0%

What to fix?

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 6316): FATAL EXCEPTION: main 6316): Process: com.medhand.WRICN PID: 6316 6316): java.lang.Runti... Users with phone manufactured by Motorola might experience a crash on their phone!. Fix now!

Must fix: App crashed because of 6316): FATAL EXCEPTION: main 6316): Process: com.medhand.WRICN PID: 6316 6316): java.lang.Runti... Users with phone manufactured by LYF might experience a crash on their phone!. Fix now!

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

Must fix: App crashed because of 6316): FATAL EXCEPTION: main 6316): Process: com.medhand.WRICN PID: 6316 6316): java.lang.Runti... Users with phone manufactured by Panasonic 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

Motorola Moto E (2nd gen) crashed at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2339) 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.

Must fix: App crashed because of 6316): FATAL EXCEPTION: main 6316): Process: com.medhand.WRICN PID: 6316 6316): java.lang.Runti... Users with phone manufactured by Lenovo might experience a crash on their phone!. Fix now!

Must fix: App crashed because of 6316): FATAL EXCEPTION: main 6316): Process: com.medhand.WRICN PID: 6316 6316): java.lang.Runti... Users with phone manufactured by Asus might experience a crash on their phone!. Fix now!

Lenovo A6000 crashed at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2308) View details

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

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

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

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

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

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

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.

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

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

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

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

45 apps having similar CPU load have low Chhi Scores

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

competition benchmark

This app is ranked #675 in Medical

670
671
672
673
674
back-to-top