App Quality Dashboard

GT Photo Recovery

0.9 / 5

Chhi Score

This app is performing

Poor

Medium Risk

/5

Good

/5

High  Risk

/5

Good

/5

#

 

Category

Rank

  • Install time: 3.62 Sec
  • Launch time: 0.30 Sec
  • Application size : 3.10 MB
  • Last tested on : 08/05/2017
  • Build ID
    :   v1.2.8
  • Chhi Score
    :   0.9
  • Change Rate
    :   0%

What to fix?

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

Must fix: App crashed because of FATAL EXCEPTION: main Process: mobi.bihu.recovery.photo PID: 19704 java.lang.ExceptionInIniti... Users with phone manufactured by Motorola 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 FATAL EXCEPTION: main Process: mobi.bihu.recovery.photo PID: 19704 java.lang.ExceptionInIniti... Users with phone manufactured by Lenovo might experience a crash on their phone!. Fix now!

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

Must fix: App crashed because of FATAL EXCEPTION: main Process: mobi.bihu.recovery.photo PID: 19704 java.lang.ExceptionInIniti... Users with phone manufactured by YU might experience a crash on their phone!. Fix now!

Must fix: App crashed because of FATAL EXCEPTION: main Process: mobi.bihu.recovery.photo PID: 19704 java.lang.ExceptionInIniti... Users with phone manufactured by Micromax might experience a crash on their phone!. Fix now!

Must fix: App crashed because of FATAL EXCEPTION: main Process: mobi.bihu.recovery.photo PID: 19704 java.lang.ExceptionInIniti... Users with phone manufactured by Samsung might experience a crash on their phone!. Fix now!

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

Utilization of CPU is close to the threshold.

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

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

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

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

Caching: Use LruCache for data caching to optimize memory usage

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

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

15 Tests crashed out of 21 Tests. Check where the app crashed. View details

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

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

43.73 MB of App Dalvik utilized by activity mobi.bihu.recovery.ui.activity.PhotoRecoveryActivity. View details

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

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

Screen coverage

Test Flows YU Yuphoria Panasonic P55 Zenfone 2 Laser Micromax Canvas AQ4502 Lenovo VIBE K4 Note Lenovo A6000 Samsung Galaxy J7 Motorola Moto E (2nd gen)

Install app

  • Crash

  • Success

  • Success

  • Crash

  • Success

  • Crash

  • Crash

  • Crash

Scenario 1

  • Crash

  • Crash

  • Crash

  • Crash

  • Crash

Scenario 2

  • Crash

  • Success

  • Success

  • Crash

  • Success

  • Crash

  • Crash

  • Crash

competition benchmark

This app is ranked #1054 in Productivity

1049
1050
1051
1052
1053
back-to-top