App Quality Dashboard

Prayer Times

3.1 / 5

Chhi Score

This app is performing

Average

Medium Risk

/5

Medium Risk

/5

Good 

/5

Good

/5

#

 

Category

Rank

  • Install time: Icon 19.55 Sec
  • Launch time: Icon 2.00 Sec
  • Application size: Icon 9.38 MB
  • Last tested on : 04/05/2017
  • Build ID
    :   v5.3.1
  • Chhi Score
    :   3.1
  • Change Rate
    :   -11.43 %

What to fix?

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

Build v5.3.0 did better in CPU . Spikes in CPU contributed to score drop by 36.36%

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

Build v5.3.0 did better in Memory . Spikes in Memory contributed to score drop by 17.65%

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

Consider re-merging the code from build v5.3.0, CPU score was 3.3

Consider re-merging the code from build v5.3.0, Memory score was 3.4

14 tests need immediate attention. View performance graph.

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

Utilization of CPU is close to the threshold.

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

35.30 MB of App Dalvik utilized by activity com.kodelokus.prayertime.PrayerTimeActivity. View details

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

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

Caching: Use LruCache for data caching to optimize memory usage

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

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

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

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

Your average App Dalvik usage surged by 42.59%, Your memory score is 2.8

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

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

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

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

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

The app's Network score has improved by 2.17% compared to build v5.3.0! Good job!

Screen Coverage

competition benchmark

This app is ranked #1526 in Lifestyle

1521
1522
1523
1524
1525
back-to-top