App Quality Dashboard

Computer Basics

3.9 / 5

Chhi Score

This app is performing

Average

Good

/5

Medium Risk

/5

Good 

/5

Medium Risk

/5

#

 

Category

Rank

  • Install time: Icon 8.43 Sec
  • Launch time: Icon 2.59 Sec
  • Application size: Icon 3.24 MB
  • Last tested on : 10/05/2017
  • Build ID
    :   v1.7
  • Chhi Score
    :   3.9
  • Change Rate
    :   0%

What to fix?

Build v1.6 did better in Network . Spikes in Network contributed to score drop by 37.78%

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

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

Build v1.6 did better in CPU . Spikes in CPU contributed to score drop by 20.83%

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 5 CPU risks.

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

5 tests need immediate attention. View performance graph.

Consider re-merging the code from build v1.6, Network score was 4.5

Consider re-merging the code from build v1.6, CPU score was 2.4

The app has a high performance risk for the phone manufacturer(s) HTC, InFocus. Check coverage report for more details.

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

Avoid wake-locks in background, using Batch and schedulers APIs such as GCM, Job schedulers could reduce wake-locks

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.

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

Network utilization on InFocus exceeded 1024 KB, you might want to consider bringing it down

Caching: Use LruCache for data caching to optimize memory usage

Fix & Optimize launch time using Flatbuffers for storage and rendering performance.

Total Network data consumed was 1568.85KB in HTC Desire 626 Dual SIM , This indicates the app will take 10-15 seconds on 2G network and 8-9 seconds on 3G network to load! View details

42.62 MB of App Dalvik utilized by activity com.bhavitech.computerbasics.ActivityMain. View details

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

There is high probability of identifying risks running the apps with conditions

Network utilization on HTC Desire 626 Dual SIM exceeded 1024 KB, you might want to consider bringing it down

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

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

Fix Oncreate() if the launch time is exceeding more than 3.2 secs. Try deflating views and layouts to optimize.

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

The app's Memory score has improved by 2.44% compared to build v1.6! Good job!

Screen coverage

competition benchmark

This app is ranked #266 in Books & Reference

261
262
263
264
265
back-to-top