App Quality Dashboard

Dictionary

1.4 / 5

Chhi Score

This app is performing

Poor

Medium Risk

/5

High Risk

/5

Good 

/5

Medium Risk

/5

#

 

Category

Rank

  • Install time: Icon 10.21 Sec
  • Launch time: Icon 6.73 Sec
  • Application size: Icon 4.99 MB
  • Last tested on : 25/04/2017
  • Build ID
    :   v6.1.3
  • Chhi Score
    :   1.4
  • Change Rate
    :   -17.65 %

What to fix?

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

Your App CPU is now in a High Risk Zone. With a small investment into your testing you can improve your app quality better. Get more test coverage

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.

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

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

Build v6.1 did better in Memory . Spikes in Memory contributed to score drop by 23.08%

Potential risk in CPU: Utilization has gone up by 7.14% compared to build v6.1

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

Build v6.1 did better in Network . Spikes in Network contributed to score drop by 12.12%

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

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

Utilization of CPU is close to the threshold.

The app took 6.73 seconds to load on Android OS version 5.0.2. Usually anything more than 3.2 seconds results in user drops. View details

27 tests need immediate attention. View performance graph.

Consider re-merging the code from build v6.1, Memory score was 2.6

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

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

42.39 MB of App Dalvik utilized by activity com.tfd.activity.MainActivity. View details

Network utilization on LYF-WATER 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

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

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

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

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

318 apps having similar CPU load have low Chhi Scores

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

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

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

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

Your average App Dalvik usage surged by 28.75%, Your memory score is 2.0

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

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

Caching: Use LruCache for data caching to optimize memory usage

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

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 #1443 in Books & Reference

1438
1439
1440
1441
1442
back-to-top