App Quality Dashboard

BOXxCAM

2.1 / 5

Chhi Score

This app is performing

Average

Medium Risk

/5

Medium Risk

/5

Good 

/5

Good

/5

#

 

Category

Rank

  • Install time: Icon 26.57 Sec
  • Launch time: Icon 1.83 Sec
  • Application size: Icon 17.46 MB
  • Last tested on : 26/03/2017
  • Build ID
    :   v1.3.6
  • Chhi Score
    :   2.1
  • Change Rate
    :   +75 %

What to fix?

App launch time went up by 12.9% initlizate network calls after few seconds of loading the resources. 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.

The app's memory score is 1.9 due to high memory utilization. Needs to be fixed as priority.

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

The app's CPU score has improved by 21.74% compared to build 1.3.4! Good job!

The app's Memory score has improved by 5.56% compared to build 1.3.4! Good job!

16 tests need immediate attention. View performance graph.

Utilization of CPU is close to the threshold.

60.42 MB of App Dalvik utilized by activity com.meitu.boxxcam.activity.EffectCameraActivity. View details

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

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

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

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

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

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

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

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

Caching: Use LruCache for data caching to optimize memory usage

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

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

The app's Network score has improved by 11.63% compared to build 1.3.4! Good job!

Well done, Network consumption has come down by 74.77 % compared to build 1.3.4

Screen Coverage

competition benchmark

This app is ranked #832 in Photography

827
828
829
830
831
back-to-top