App Quality Dashboard

Qup

1.7 / 5

Chhi Score

This app is performing

Poor

Medium Risk

/5

Medium Risk

/5

Good 

/5

High Risk

/5

#

 

Category

Rank

  • Install time: Icon 7.33 Sec
  • Launch time: Icon 1.90 Sec
  • Application size: Icon 5.59 MB
  • Last tested on : 24/05/2017
  • Build ID
    :   v1.19
  • Chhi Score
    :   1.7
  • Change Rate
    :   -10.53 %

What to fix?

Fixing Network risks could drastically improve Chhi Score. There are 9 Network risks.

Build v1.18 did better in CPU . Spikes in CPU contributed to score drop by 41.94%

Build v1.18 did better in Memory . Spikes in Memory contributed to score drop by 19.35%

App launch time went up by INF% initlizate network calls after few seconds of loading the resources. View details

Fixing CPU risks could drastically improve Chhi Score. There are 9 CPU risks.

9 Risk(s) are due to Data Sent/Received in Network exceeding the threshold.

9 Risk(s) are due to Threads in CPU exceeding the threshold.

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 CPU Load in CPU exceeding the threshold.

Consider re-merging the code from build v1.18, CPU score was 3.1

Consider re-merging the code from build v1.18, Memory score was 3.1

The app has a high performance risk for the phone manufacturer(s) Karbonn, Spice, YU, Panasonic, Motorola, OnePlus. Check coverage report for more details.

9 tests need immediate attention. View performance graph.

Utilization of CPU is close to the threshold.

Your average App Dalvik usage surged by 58.93%, Your memory score is 2.5

Network utilization on Motorola Moto G 2014 XT1068 Dual 8GB 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

Printing logs on callbacks would make debugging easy for tests run in our platform

Coverage: Android version coverage for reports will range between 5.1.1 to 7.1.2

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.

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.

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

Upload APKs with and without 3rd Party SDKs to monitor and optimize the impact of app performance

Network utilization on Motorola Moto E (2nd gen) exceeded 1024 KB, you might want to consider bringing it down

App makes 3107.15 KB of network requests. Moving this to a background thread will improve load speed. View details

Caching: Use LruCache for data caching to optimize memory usage

47.51 MB of App Dalvik utilized by activity app.com.qproject.MainActivity. View details

Total Network data consumed was 3107.15KB in Motorola Moto G 2014 XT1068 Dual 8GB , This indicates the app will take 10-15 seconds on 2G network and 8-9 seconds on 3G network to load! View details

Optimize the app to render elements at 60 FPS for buttery smooth experience.

Below 10 MB approach would increase app installs in crowded markets such as India, China and Russia!

Screen Coverage

competition benchmark

This app is ranked #606 in Medical

601
602
603
604
605
back-to-top