App Quality Dashboard

Hindu Calendar

1.7 / 5

Chhi Score

This app is performing

Poor

Medium Risk

/5

High Risk

/5

Good 

/5

High Risk

/5

#

 

Category

Rank

  • Install time: 5.33 Sec
  • Launch time: 1.51 Sec
  • Application size : 3.13 MB
  • Last tested on : 18/04/2017
  • Build ID
    :   v6.3.1
  • Chhi Score
    :   1.7
  • Change Rate
    :   0%

What to fix?

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

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

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

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

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

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

15 tests need immediate attention. View performance graph.

Utilization of CPU is close to the threshold.

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

Make sure your App's PSS isn't too high. Freeing objects that aren't needed would reduce chances of getting unexpectedly killed by Android system.

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

44.91 MB of App Dalvik utilized by activity com.alokmandavgane.hinducalendar.MainActivity. View details

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

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

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

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

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.

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

318 apps having similar CPU load have low Chhi Scores

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

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!

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

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

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

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

Network utilization on Lava Iris X8 exceeded 1024 KB, you might want to consider bringing it down

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

Screen coverage

Test Flows YU Yuphoria Lava Iris X8 Panasonic P55 Karbonn Titanium Machfive Micromax Canvas AQ4502 Lenovo VIBE K4 Note Samsung Galaxy J7 Motorola Moto E (2nd gen)

Install app

  • Risk

  • Risk

  • Risk

  • Risk

  • Risk

  • Risk

  • Risk

  • Risk

Scenario 1

  • Risk

  • Risk

  • Risk

  • Risk

  • Risk

  • Risk

  • Risk

competition benchmark

This app is ranked #1308 in Books & Reference

1303
1304
1305
1306
1307
back-to-top