App Quality Dashboard

My Name Greetings

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 8.58 Sec
  • Launch time: Icon 1.59 Sec
  • Application size: Icon 5.44 MB
  • Last tested on : 30/03/2017
  • Build ID
    :   v1.0.4
  • Chhi Score
    :   3.6
  • Change Rate
    :   +71.43 %

Insights (27)

What to fix?

12 Risk(s) are due to Threads in CPU exceeding the threshold.
Fixing CPU risks could drastically improve Chhi Score. There are 12 CPU risks.
App launch time went up by 20.45% 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.
1 Risk(s) are due to Data Sent/Received in Network exceeding the threshold.
The app's CPU score has improved by 22.22% compared to build v1.0.2! Good job!
The app has a high performance risk for the phone manufacturer(s) LYF, Motorola, Panasonic, Lava, Lenovo. Check coverage report for more details.
Utilization of CPU is close to the threshold.
The app's Memory score has improved by 3.03% compared to build v1.0.2! Good job!
12 tests need immediate attention. View performance graph.
Build v1.0.2 did better in Network . Spikes in Network contributed to score drop by 4.55%
57.60 MB of App Dalvik utilized by activity com.vpmobisolution.mynamegreetings.SelectImage. View details
Optimize the app to render elements at 60 FPS for buttery smooth experience.
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
Fix & Optimize launch time using Flatbuffers for storage and rendering performance.
Follow simple UI hierarchy by reducing nested layouts to Relative layouts.
Do not initialize objects that aren't necessary during launch times. Moving to singleton pattern helps
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.
Caching: Use LruCache for data caching to optimize memory usage
App makes 1036.64 KB of network requests. Moving this to a background thread will improve load speed. View details
Coverage: Android version coverage for reports will range between 5.1.1 to 7.1.2
Below 10 MB approach would increase app installs in crowded markets such as India, China and Russia!
Testability: Providing login / sign-up details could very well improve depth of bot clicks
Printing logs on callbacks would make debugging easy for tests run in our platform
Network utilization on Lava Iris X8 exceeded 1024 KB, you might want to consider bringing it down
Unlock more fixes
competition benchmark

This app is ranked #608 in Entertainment

603
604
605
606
607
back-to-top