App Quality Dashboard

Makeup

1.2 / 5

Chhi Score

This app is performing

Poor

High Risk

/5

Medium Risk

/5

Good 

/5

Medium Risk

/5

#

 

Category

Rank

  • Install time: 12.24 Sec
  • Launch time: 0.35 Sec
  • Application size : 8.99 MB
  • Last tested on : 30/04/2017
  • Build ID
    :   v1.3.0
  • Chhi Score
    :   1.2
  • Change Rate
    :   0%

What to fix?

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

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

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 21 CPU risks.

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

24 tests need immediate attention. View performance graph.

Utilization of CPU is close to the threshold.

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

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

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

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

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

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

83.23 MB of App Dalvik utilized by activity makeup.berzanov.com.makeup.Makeup. View details

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

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

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

Screen Coverage

competition benchmark

This app is ranked #3285 in Lifestyle

3280
3281
3282
3283
3284
back-to-top