App Quality Dashboard

HD Camera

2.2 / 5

Chhi Score

This app is performing

Average

Good

/5

Medium Risk

/5

High  Risk

/5

Good

/5

#

 

Category

Rank

  • Install time: 3.76 Sec
  • Launch time: 5.13 Sec
  • Application size : 1.98 MB
  • Last tested on : 26/04/2017
  • Build ID
    :   v1.0.0M
  • Chhi Score
    :   2.2
  • Change Rate
    :   0%

What to fix?

Karbonn Titanium Machfive crashed at com.google.android.gms.ads.internal.ar.(Unknown Source) View details

Oops!, The app crashed on Karbonn Titanium Machfive, Panasonic P55 & more devices. View details

Panasonic P55 crashed at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2572) 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.

Fixing CPU risks could drastically improve Chhi Score. There are 7 CPU risks.

7 Risk(s) are due to Threads in CPU exceeding the threshold.

1 Risk(s) are due to Data Sent/Received in Network exceeding the threshold.

Must fix: App crashed because of FATAL EXCEPTION: main Process: com.appmaker.camera.hd PID: 26481 java.lang.RuntimeException: Un... Users with phone manufactured by Panasonic might experience a crash on their phone!. Fix now!

Must fix: App crashed because of FATAL EXCEPTION: main Process: com.appmaker.camera.hd PID: 26481 java.lang.RuntimeException: Un... Users with phone manufactured by Karbonn might experience a crash on their phone!. Fix now!

The app took 5.13 seconds to load on Android OS version 5.0.2. Usually anything more than 3.2 seconds results in user drops. View details

7 tests need immediate attention. View performance graph.

Utilization of CPU is close to the threshold.

Utilization of Memory is close to the threshold.

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

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

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

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

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

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

App makes 1842.02 KB of network requests. Moving this to a background thread will improve load speed. View details

38.75 MB of App Dalvik utilized by activity com.appmaker.camera.hd.MainActivity. View details

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

6 Tests crashed out of 17 Tests. Check where the app crashed. View details

Network utilization on Lenovo A6000 exceeded 1024 KB, you might want to consider bringing it down

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

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

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

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

Caching: Use LruCache for data caching to optimize memory usage

Screen coverage

competition benchmark

This app is ranked #786 in Photography

781
782
783
784
785
back-to-top