App Quality Dashboard

Twitter

3.9 / 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 45.89 Sec
  • Launch time: Icon 1.20 Sec
  • Application size: Icon 31.19 MB
  • Last tested on : 29/03/2017
  • Build ID
    :   v6.39.0
  • Chhi Score
    :   3.9
  • Change Rate
    :   0%

Insights (25)

What to fix?

Fixing CPU risks could drastically improve Chhi Score. There are 2 CPU risks.
2 Risk(s) are due to Threads in CPU exceeding the threshold.
Build v6.37.0 did better in CPU . Spikes in CPU contributed to score drop by 3.45%
App launch time went up by 122.22% 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.
Build v6.37.0 did better in Network . Spikes in Network contributed to score drop by 2%
3 tests need immediate attention. View performance graph.
Utilization of CPU is close to the threshold.
The app has a high performance risk for the phone manufacturer(s) Panasonic, Micromax, YU. Check coverage report for more details.
Build v6.37.0 did better in Memory . Spikes in Memory contributed to score drop by 2.56%
40.06 MB of App Dalvik utilized by activity com.twitter.android.FlowActivity. View details
Avoid wake-locks in background, using Batch and schedulers APIs such as GCM, Job schedulers could reduce wake-locks
Fix & Optimize launch time using Flatbuffers for storage and rendering performance.
Fix Oncreate() if the launch time is exceeding more than 3.2 secs. Try deflating views and layouts to optimize.
Optimize the app to render elements at 60 FPS for buttery smooth experience.
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
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
Caching: Use LruCache for data caching to optimize memory usage
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!
Your average App Dalvik usage surged by 7.2%, Your memory score is 3.8
There is high probability of identifying risks running the apps with conditions
Testability: Providing login / sign-up details could very well improve depth of bot clicks
Unlock more fixes

Testing depth

Covered

32%

Uncovered

68%

Depth Details

competition benchmark

This app is ranked #229 in News & Magazines

224
225
226
227
228
back-to-top