App Quality Dashboard

iSearch

0.1 / 5

Chhi Score

This app is performing

Poor

Memory

CPU

High  Risk

/5

network

#

 

Category

Rank

  • Install time: 2.10 Sec
  • Launch time: 0.00 Sec
  • Application size : 0.53 MB
  • Last tested on : 28/04/2017
  • Build ID
    :   v1.22
  • Chhi Score
    :   0.1
  • Change Rate
    :   0%

What to fix?

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

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

Must fix: App crashed because of 5807): FATAL EXCEPTION: main 5807): Process: com.infolife.iSearch PID: 5807 5807): java.lang.... Users with phone manufactured by Panasonic might experience a crash on their phone!. Fix now!

Must fix: App crashed because of 5807): FATAL EXCEPTION: main 5807): Process: com.infolife.iSearch PID: 5807 5807): java.lang.... Users with phone manufactured by YU 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

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.

Motorola Moto E (2nd gen) crashed at java.lang.reflect.Constructor.newInstance(Native Method) View details

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

Lenovo A6000 crashed at java.lang.reflect.Constructor.newInstance(Native Method) View details

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

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

Must fix: App crashed because of 5807): FATAL EXCEPTION: main 5807): Process: com.infolife.iSearch PID: 5807 5807): java.lang.... Users with phone manufactured by Lava might experience a crash on their phone!. Fix now!

Must fix: App crashed because of 5807): FATAL EXCEPTION: main 5807): Process: com.infolife.iSearch PID: 5807 5807): java.lang.... Users with phone manufactured by Micromax might experience a crash on their phone!. Fix now!

Must fix: App crashed because of 5807): FATAL EXCEPTION: main 5807): Process: com.infolife.iSearch PID: 5807 5807): java.lang.... 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

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

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

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

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

318 apps having similar CPU load have low Chhi Scores

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

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

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

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

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

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

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

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

competition benchmark

This app is ranked #1631 in Books & Reference

1626
1627
1628
1629
1630
back-to-top