App Quality Dashboard

Simple Mehandi Designs HD

3.3 / 5

Chhi Score

This app is performing


Medium Risk


Medium Risk


Medium  Risk








  • Install time: Icon 16.45 Sec
  • Launch time: --- 3.00 Sec
  • Application size: Icon 11.34 MB
  • Last tested on : 27/03/2017
  • Build ID
    :   v1.0.0.2
  • Chhi Score
    :   3.3
  • Change Rate
    :   -15.38 %

What to fix?

Build v1.0.0.1 did better in CPU . Spikes in CPU contributed to score drop by 27.5%

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

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

Must fix: App crashed because of FATAL EXCEPTION: main Process: PID: 26010 java.lang.RuntimeE... Users with phone manufactured by Lava might experience a crash on their phone!. Fix now!

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.

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

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

Build v1.0.0.1 did better in Memory . Spikes in Memory contributed to score drop by 13.95%

5 tests need immediate attention. View performance graph.

Utilization of CPU is close to the threshold.

App size increased by 34.2% See how to optimize.

Build v1.0.0.1 did better in Network . Spikes in Network contributed to score drop by 6.38%

Consider re-merging the code from build v1.0.0.1, CPU score was 4.0

Motorola Moto E (2nd gen), Lava Iris X8, Lenovo VIBE K4 Note has moved from Good to Medium risk due to RISK . View details

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

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

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

Your average App Dalvik usage surged by 26.37%, Your memory score is 3.7

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

Caching: Use LruCache for data caching to optimize memory usage

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

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

3 Tests crashed out of 11 Tests. Check where the app crashed. View details

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

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

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

The app has crashed on few device(s)! View details

52.43 MB of App Dalvik utilized by activity View details

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

Screen Coverage

competition benchmark

This app is ranked #1153 in Lifestyle