App Quality Dashboard

Step by Step Salah

3.9 / 5

Chhi Score

This app is performing




Medium Risk


Medium  Risk








  • Install time: Icon 20.67 Sec
  • Launch time: Icon 0.46 Sec
  • Application size: --- 36.86 MB
  • Last tested on : 26/05/2017
  • Build ID
    :   v2.5
  • Chhi Score
    :   3.9
  • Change Rate
    :   +11.43 %

What to fix?

Must fix: App crashed because of 1207): FATAL EXCEPTION: Thread-2745 1207): Process: com.quranreading.stepbystepsalat PID: 1207... Users with phone manufactured by HTC might experience a crash on their phone!. Fix now!

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

Build v2.4 did better in CPU . Spikes in CPU contributed to score drop by 14.81%

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

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

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.

Utilization of CPU is close to the threshold.

6 tests need immediate attention. View performance graph.

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

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

42.32 MB of App Dalvik utilized by activity com.quranreading.stepbystepsalat.MainActivity. View details

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

The app has crashed on few device(s)! View details

Caching: Use LruCache for data caching to optimize memory usage

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

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

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

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

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

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

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

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

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

Well done, Network consumption has come down by 96.08 % compared to build v2.4

The app's Memory score has improved by 12.82% compared to build v2.4! Good job!

The app's Network score has improved by 6.38% compared to build v2.4! Good job!

Screen Coverage

competition benchmark

This app is ranked #439 in Education