App Quality Dashboard

Life Essentials

1.5 / 5

Chhi Score

This app is performing

Poor

Medium Risk

/5

Medium Risk

/5

Good 

/5

High Risk

/5

#

 

Category

Rank

  • Install time: 34.20 Sec
  • Launch time: 1.12 Sec
  • Application size : 48.19 MB
  • Last tested on : 24/03/2017
  • Build ID
    :   v5.0
  • Chhi Score
    :   1.5
  • Change Rate
    :   0%

What to fix?

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

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

Fixing CPU risks could drastically improve Chhi Score. There are 4 CPU 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.

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

7 Risk(s) are due to App PSS in Memory exceeding the threshold. See how to optimize memory and remove 7 High Risk(s).

Utilization of CPU is close to the threshold.

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

7 tests need immediate attention. View performance graph.

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

5 Risk(s) are due to App Total in Memory exceeding the threshold.

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

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

Testability: Providing login / sign-up details could very well improve depth of bot clicks

Total Network data consumed was 4194.50KB 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

74.15 MB of App Dalvik utilized by activity org.appcelerator.titanium.TiActivity. View details

Follow simple UI hierarchy by reducing nested layouts to Relative layouts.

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!

Do not initialize objects that aren't necessary during launch times. Moving to singleton pattern helps

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

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

Network utilization on Motorola Moto E (2nd gen) 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

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

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

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

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

Screen coverage

competition benchmark

This app is ranked #1391 in Books & Reference

1386
1387
1388
1389
1390
back-to-top