App Quality Dashboard

Lucky Stone Finder - English

3.0 / 5

Chhi Score

This app is performing

Average

Memory

Medium Risk

/5

CPU

Medium Risk

/5

crash

Medium  Risk

/5

network

Good

/5

Competition

#

 

Category

Rank

  • Install time: Icon 14.31 Sec
  • Launch time: Icon 0.55 Sec
  • Application size: Icon 7.86 MB
  • Last tested on : 10/05/2017
  • Build ID
    :   v1.3
  • Chhi Score
    :   3.0
  • Change Rate
    :   +25 %

Insights (30)

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.
Fixing CPU risks could drastically improve Chhi Score. There are 9 CPU risks.
Must fix: App crashed because of 4374): FATAL EXCEPTION: main 4374): Process: com.kollywoodapps.luckystonefinder_english PID: 43... Users with phone manufactured by Lava might experience a crash on their phone!. Fix now!
9 Risk(s) are due to Threads in CPU exceeding the threshold.
Build v1.2 did better in Memory . Spikes in Memory contributed to score drop by 13.16%
Consider re-merging the code from build v1.2, Memory score was 3.8
The app has a high performance risk for the phone manufacturer(s) Lava, LYF, Lenovo, Panasonic. Check coverage report for more details.
Lava Iris X8, Panasonic P55, Lenovo VIBE K4 Note has moved from Good to Medium risk due to RISK . View details
9 tests need immediate attention. View performance graph.
App size increased by 42.39% See how to optimize.
The app's CPU score has improved by 13.64% compared to build v1.2! Good job!
62.44 MB of App Dalvik utilized by activity com.kollywoodapps.luckystonefinder_english.MainActivity. View details
Testability: Providing login / sign-up details could very well improve depth of bot clicks
Caching: Use LruCache for data caching to optimize memory usage
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
Coverage: Android version coverage for reports will range between 5.1.1 to 7.1.2
3 Tests crashed out of 13 Tests. Check where the app crashed. View details
Your average App Dalvik usage surged by 24.61%, Your memory score is 3.3
Fix Oncreate() if the launch time is exceeding more than 3.2 secs. Try deflating views and layouts to optimize.
Below 10 MB approach would increase app installs in crowded markets such as India, China and Russia!
Follow simple UI hierarchy by reducing nested layouts to Relative layouts.
Optimize the app to render elements at 60 FPS for buttery smooth experience.
Fix & Optimize launch time using Flatbuffers for storage and rendering performance.
There is high probability of identifying risks running the apps with conditions
Avoid wake-locks in background, using Batch and schedulers APIs such as GCM, Job schedulers could reduce wake-locks
The app has crashed on few device(s)! View details
Do not initialize objects that aren't necessary during launch times. Moving to singleton pattern helps
The app's Network score has improved by 300% compared to build v1.2! Good job!
Well done, Network consumption has come down by 96.21 % compared to build v1.2
Unlock more fixes

Screen Coverage

competition benchmark

This app is ranked #1556 in Lifestyle

1551
1552
1553
1554
1555
back-to-top