App Quality Dashboard

Photos

0.1 / 5

Chhi Score

This app is performing

Poor

Memory

CPU

High  Risk

/5

network

#

 

Category

Rank

  • Install time: Icon 23.00 Sec
  • Launch time: Icon 0.00 Sec
  • Application size: Icon 27.01 MB
  • Last tested on : 22/03/2017
  • Build ID
    :   v2.11.0.150493453
  • Chhi Score
    :   0.1
  • Change Rate
    :   -90.91 %

What to fix?

Must fix: App crashed because of FATAL EXCEPTION: main Process: com.google.android.apps.photos PID: 25102 java.lang.UnsatisfiedL... Users with phone manufactured by Lava 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

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.

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

The app has a high performance risk for the phone manufacturer(s) Lava. Check coverage report for more details.

Consider re-merging the code from build v2.11.0.150122737, CPU score was 4.3

Consider re-merging the code from build v2.11.0.150122737, Memory score was 4.1

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

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

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

355 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!

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

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

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

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

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

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

Caching: Use LruCache for data caching to optimize memory usage

The app has crashed on few device(s)! View details

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

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

Testing depth

Covered

27%

Uncovered

73%

Depth Details

competition benchmark

This app is ranked #1038 in Photography

1033
1034
1035
1036
1037
back-to-top