App Quality Dashboard

SelfieCity

2.2 / 5

Chhi Score

This app is performing

Average

Medium Risk

/5

Medium Risk

/5

High  Risk

/5

High Risk

/5

#

 

Category

Rank

  • Install time: Icon 29.14 Sec
  • Launch time: Icon 6.35 Sec
  • Application size: Icon 18.94 MB
  • Last tested on : 29/03/2017
  • Build ID
    :   v2.7.9.0
  • Chhi Score
    :   2.2
  • Change Rate
    :   +4.76 %

What to fix?

Must fix: App crashed because of FATAL EXCEPTION: main Process: com.meitu.wheecam PID: 12770 java.lang.RuntimeException: Unable ... Users with phone manufactured by Asus might experience a crash on their phone!. Fix now!

Must fix: App crashed because of FATAL EXCEPTION: main Process: com.meitu.wheecam PID: 12770 java.lang.RuntimeException: Unable ... Users with phone manufactured by LYF might experience a crash on their phone!. Fix now!

Zenfone 2 Laser crashed at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2434) View details

Karbonn Titanium Machfive crashed at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2455) View details

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

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

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.

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

Must fix: App crashed because of FATAL EXCEPTION: main Process: com.meitu.wheecam PID: 12770 java.lang.RuntimeException: Unable ... Users with phone manufactured by Karbonn might experience a crash on their phone!. Fix now!

Oops!, The app crashed on Zenfone 2 Laser , Karbonn Titanium Machfive & more devices. View details

Must fix: App crashed because of FATAL EXCEPTION: main Process: com.meitu.wheecam PID: 12770 java.lang.RuntimeException: Unable ... 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.meitu.wheecam PID: 12770 java.lang.RuntimeException: Unable ... Users with phone manufactured by YU might experience a crash on their phone!. Fix now!

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

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

App launch time went up by 291.67% initlizate network calls after few seconds of loading the resources. View details

The app's CPU score has improved by 35.71% compared to build v2.6.9.0! Good job!

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

Utilization of CPU is close to the threshold.

13 tests need immediate attention. View performance graph.

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

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

10 Tests crashed out of 22 Tests. Check where the app crashed. View details

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

Network utilization on Zenfone 2 Laser exceeded 1024 KB, you might want to consider bringing it down

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

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

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

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

Total Network data consumed was 7809.93KB 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

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

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

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

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

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

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

49.74 MB of App Dalvik utilized by activity com.meitu.wheecam.WheeCamMainActivity. View details

Caching: Use LruCache for data caching to optimize memory usage

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

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

The app's Memory score has improved by 5.41% compared to build v2.6.9.0! Good job!

Well done, Network consumption has come down by 52.51 % compared to build v2.6.9.0

Screen Coverage

competition benchmark

This app is ranked #811 in Photography

806
807
808
809
810
back-to-top