App Quality Dashboard

Recipes and Health Tips

3.7 / 5

Chhi Score

This app is performing


Medium Risk


Medium Risk


Medium  Risk








  • Install time: Icon 11.67 Sec
  • Launch time: Icon 0.84 Sec
  • Application size: Icon 5.26 MB
  • Last tested on : 13/05/2017
  • Build ID
    :   v1.8
  • Chhi Score
    :   3.7
  • Change Rate
    :   +23.33 %

What to fix?

Must fix: App crashed because of FATAL EXCEPTION: Thread-12 Process: com.laks.recipeshealthtips PID: 32352 java.util.ConcurrentM... Users with phone manufactured by Motorola might experience a crash on their phone!. Fix now!

App launch time went up by 126.92% 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 CPU score has improved by 12.5% compared to build v1.7! Good job!

Utilization of CPU is close to the threshold.

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

Motorola Nexus 6 has moved from Good to Medium risk due to FAIL . View details

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

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

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

21.00 MB of App Dalvik utilized by activity com.laks.recipeshealthtips.Category. View details

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

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

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

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

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

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

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

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!

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

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

The app's Memory score has improved by 48.15% compared to build v1.7! Good job!

The app's Network score has improved by 17.95% compared to build v1.7! Good job!

Well done, Network consumption has come down by 66.39 % compared to build v1.7

Screen Coverage

competition benchmark

This app is ranked #94 in Food & Drink