App Quality Dashboard

Camera

1.5 / 5

Chhi Score

This app is performing

Poor

Medium Risk

/5

Medium Risk

/5

Good 

/5

High Risk

/5

#

 

Category

Rank

  • Install time: Icon 7.50 Sec
  • Launch time: Icon 0.00 Sec
  • Application size: Icon 3.08 MB
  • Last tested on : 09/03/2017
  • Build ID
    :   v1.1.2
  • Chhi Score
    :   1.5
  • Change Rate
    :   -48.28 %

What to fix?

4 Risk(s) are due to App PSS in Memory exceeding the threshold. See how to optimize memory and remove 4 High Risk(s).

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

Fixing Network risks could drastically improve Chhi Score. There are 4 Network risks.

Build v1.1.1 did better in Memory . Spikes in Memory contributed to score drop by 15.38%

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

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.

Potential risk in Network: Utilization has gone up by70% compared to build v1.1.1

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

Consider re-merging the code from build v1.1.1, Network score was 4.0

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

Make sure your App's PSS isn't too high. Freeing objects that aren't needed would reduce chances of getting unexpectedly killed by Android system.

4 tests need immediate attention. View performance graph.

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

Caching: Use LruCache for data caching to optimize memory usage

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

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

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

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

Your average App Dalvik usage surged by 16.85%, Your memory score is 2.2

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

Network utilization on YU Yuphoria exceeded 1024 KB, you might want to consider bringing it down

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

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

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

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

25.98 MB of App Dalvik utilized by activity net.ijoysoft.camera.activity.CameraActivity. View details

Total Network data consumed was 3099.17KB in Lenovo A6000 , This indicates the app will take 10-15 seconds on 2G network and 8-9 seconds on 3G network to load! View details

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

Screen coverage

competition benchmark

This app is ranked #937 in Photography

932
933
934
935
936
back-to-top