App Quality Dashboard

Calling Codes

2.7 / 5

Chhi Score

This app is performing

Average

Medium Risk

/5

Medium Risk

/5

Good 

/5

Medium Risk

/5

#

 

Category

Rank

  • Install time: 8.00 Sec
  • Launch time: 1.30 Sec
  • Application size : 2.85 MB
  • Last tested on : 16/04/2017
  • Build ID
    :   v2.0
  • Chhi Score
    :   2.7
  • Change Rate
    :   0%

What to fix?

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.

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

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

The app's memory score is 2.5 due to high memory utilization. Needs to be fixed as priority.

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

4 tests need immediate attention. View performance graph.

App makes 3292.84 KB of network requests. Moving this to a background thread will improve load speed. View 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

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

Total Network data consumed was 3292.84KB in Samsung Galaxy J7 , This indicates the app will take 10-15 seconds on 2G network and 8-9 seconds on 3G network to load! View details

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

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

43.91 MB of App Dalvik utilized by activity com.slangstudios.countrycodes.SplashScreen. View details

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

Caching: Use LruCache for data caching to optimize memory usage

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

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

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

Network utilization on Samsung Galaxy J7 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

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

competition benchmark

This app is ranked #703 in Travel & Local

698
699
700
701
702
back-to-top