App Quality Dashboard

AAP News

2.4 / 5

Chhi Score

This app is performing

Average

Memory

Medium Risk

/5

CPU

Medium Risk

/5

crash

Good 

/5

network

Medium Risk

/5

Competition

#

 

Category

Rank

  • Install time: Icon 26.50 Sec
  • Launch time: Icon 7.55 Sec
  • Application size: Icon 9.49 MB
  • Last tested on : 08/05/2017
  • Build ID
    :   v32.0
  • Chhi Score
    :   2.4
  • Change Rate
    :   +60 %

Insights (35)

What to fix?

Fixing Network risks could drastically improve Chhi Score. There are 5 Network risks.
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.
5 Risk(s) are due to Data Sent/Received in Network exceeding the threshold.
Build v27.0 did better in Memory . Spikes in Memory contributed to score drop by 4.55%
Do not initialize objects that aren't necessary during launch times. Moving to singleton pattern helps
Build v27.0 did better in CPU . Spikes in CPU contributed to score drop by 3.7%
11 Risk(s) are due to App PSS in Memory exceeding the threshold. See how to optimize memory and remove 11 High Risk(s).
1 Risk(s) are due to Threads in CPU exceeding the threshold.
12 tests need immediate attention. View performance graph.
The app has a high performance risk for the phone manufacturer(s) Karbonn, YU, Lenovo, LYF, Motorola, Panasonic, Micromax, Asus. Check coverage report for more details.
App size increased by 41.85% See how to optimize.
The app's Network score has improved by 18.75% compared to build v27.0! Good job!
The app's memory score is 2.1 due to high memory utilization. Needs to be fixed as priority.
Utilization of CPU is close to the threshold.
2 Risk(s) are due to App Total in Memory exceeding the threshold.
The app took 7.55 seconds to load on Android OS version 5.0.2. Usually anything more than 3.2 seconds results in user drops. View details
Make sure your App's PSS isn't too high. Freeing objects that aren't needed would reduce chances of getting unexpectedly killed by Android system.
Network utilization on Lenovo A6000 exceeded 1024 KB, you might want to consider bringing it down
Testability: Providing login / sign-up details could very well improve depth of bot clicks
Network utilization on Motorola Moto E (2nd gen) exceeded 1024 KB, you might want to consider bringing it down
App makes 1228.04 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
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!
There is high probability of identifying risks running the apps with conditions
Printing logs on callbacks would make debugging easy for tests run in our platform
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
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.
Upload APKs with and without 3rd Party SDKs to monitor and optimize the impact of app performance
88.12 MB of App Dalvik utilized by activity com.texterity.android.AAPNews.activities.SplashActivity. View details
Total Network data consumed was 1228.04KB in Motorola Moto E (2nd gen) , This indicates the app will take 10-15 seconds on 2G network and 8-9 seconds on 3G network to load! View details
Fix & Optimize launch time using Flatbuffers for storage and rendering performance.
Unlock more fixes

Screen coverage

competition benchmark

This app is ranked #532 in Medical

527
528
529
530
531
back-to-top