App Quality Dashboard

Indian Recipes

3.6 / 5

Chhi Score

This app is performing

Average

Memory

Medium Risk

/5

CPU

Medium Risk

/5

crash

Good 

/5

network

Good

/5

Competition

#

 

Category

Rank

  • Install time: Icon 12.50 Sec
  • Launch time: Icon 0.90 Sec
  • Application size: Icon 6.65 MB
  • Last tested on : 02/05/2017
  • Build ID
    :   v20.7.0
  • Chhi Score
    :   3.6
  • Change Rate
    :   +44 %

Insights (28)

What to fix?

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.
Build v20.0.1 did better in Memory . Spikes in Memory contributed to score drop by 15%
App launch time went up by INF% initlizate network calls after few seconds of loading the resources. View details
4 Risk(s) are due to Threads in CPU exceeding the threshold.
Fixing CPU risks could drastically improve Chhi Score. There are 4 CPU risks.
Build v20.0.1 did better in CPU . Spikes in CPU contributed to score drop by 25.93%
Consider re-merging the code from build v20.0.1, CPU score was 2.7
Consider re-merging the code from build v20.0.1, Memory score was 4.0
App size increased by 12.14% See how to optimize.
The app has a high performance risk for the phone manufacturer(s) Asus, LYF. Check coverage report for more details.
4 tests need immediate attention. View performance graph.
Follow simple UI hierarchy by reducing nested layouts to Relative layouts.
Printing logs on callbacks would make debugging easy for tests run in our platform
45.00 MB of App Dalvik utilized by activity com.endless.indianrecipes.MainActivity. View details
There is high probability of identifying risks running the apps with conditions
Upload APKs with and without 3rd Party SDKs to monitor and optimize the impact of app performance
Below 10 MB approach would increase app installs in crowded markets such as India, China and Russia!
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.
Avoid wake-locks in background, using Batch and schedulers APIs such as GCM, Job schedulers could reduce wake-locks
Optimize the app to render elements at 60 FPS for buttery smooth experience.
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
Your average App Dalvik usage surged by 41.81%, Your memory score is 3.4
Coverage: Android version coverage for reports will range between 5.1.1 to 7.1.2
Fix & Optimize launch time using Flatbuffers for storage and rendering performance.
Well done, Network consumption has come down by 80.39 % compared to build v20.0.1
The app's Network score has improved by 186.67% compared to build v20.0.1! Good job!
Unlock more fixes

Screen Coverage

competition benchmark

This app is ranked #107 in Food & Drink

102
103
104
105
106
back-to-top