App Quality Dashboard

CallApp Contacts

0.1 / 5

Chhi Score

This app is performing

Poor

Memory

CPU

High  Risk

/5

network

#

 

Category

Rank

  • Install time: Icon 22.75 Sec
  • Launch time: --- 0.00 Sec
  • Application size: Icon 17.08 MB
  • Last tested on : 19/05/2017
  • Build ID
    :   v1.207
  • Chhi Score
    :   0.1
  • Change Rate
    :   0%

What to fix?

Must fix: App crashed because of 8324): FATAL EXCEPTION: main 8324): Process: com.callapp.contacts PID: 8324 8324): java.lang.... Users with phone manufactured by Motorola might experience a crash on their phone!. Fix now!

Must fix: App crashed because of 8324): FATAL EXCEPTION: main 8324): Process: com.callapp.contacts PID: 8324 8324): java.lang.... Users with phone manufactured by Samsung 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.

Must fix: App crashed because of 8324): FATAL EXCEPTION: main 8324): Process: com.callapp.contacts PID: 8324 8324): java.lang.... Users with phone manufactured by HTC 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

Samsung Galaxy S Duos 2 S7582 crashed at java.lang.reflect.Constructor.constructNative(Native Method) at java.lang.reflect.Constructor.newInstance(Constructor.java:417) View details

Motorola Nexus 6 crashed at java.lang.Class.classForName(Native Method) View details

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 8324): FATAL EXCEPTION: main 8324): Process: com.callapp.contacts PID: 8324 8324): java.lang.... Users with phone manufactured by InFocus might experience a crash on their phone!. Fix now!

Oops!, The app crashed on Samsung Galaxy S Duos 2 S7582, Motorola Nexus 6 & more devices. View details

The app has a high performance risk for the phone manufacturer(s) HTC, Motorola, Samsung, InFocus. Check coverage report for more details.

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

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

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

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

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

98 apps having similar CPU load have low Chhi Scores

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

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

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

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.

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

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

Caching: Use LruCache for data caching to optimize memory usage

competition benchmark

This app is ranked #647 in Communication

642
643
644
645
646
back-to-top