When a prayer’s time begins, the apps you chose step aside until you have prayed. That is the whole promise of the Shield in Awwab. This post explains how it actually works, on iPhone and on Android, what it can and can’t see, and where its honest limits are.
We wrote it because a tool that sits between you and your phone deserves to be understood. You should know exactly what it does at the moment the adhān would sound, what happens when you tap each button, and what it never does with your data. Nothing here is a secret, and nothing in it is more complicated than it needs to be. It exists to protect one thing the Prophet ﷺ named as the deed God loves most: “prayer at its time” (Ṣaḥīḥ al-Bukhārī 527, Ṣaḥīḥ Muslim 85).
The idea in one minute
- You choose the apps that tend to pull you away at prayer time. Only those are held.
- When each of the five prayer times begins, those apps are paused for that prayer’s window.
- Open one, and instead of the feed you see a verse and two choices: “Go to prayer” or “I have a reason”.
- Mark the prayer as prayed, and everything unlocks at once.
- If a window passes unprayed, nothing punishes you. The Shield simply moves on to the next prayer when its time begins.
Everything happens on your phone. Awwab has no server that knows when you pray, and the Shield never sends anything to us.
Prayer windows, worked out on your phone
Each prayer has a window, not a single moment: Dhuhr runs until ʿAṣr, ʿAṣr until Maghrib, and so on (Qur’an 4:103). Awwab calculates the five times on the phone from your location, your calculation method and your Asr school, with no connection needed. Our guide to how prayer times are calculated explains the methods.
The Shield follows those windows. A prayer’s window runs from its start to the start of the next prayer, and ʿIshāʾ stays held through the night until Fajr. If you have already marked a prayer as prayed, its window passes with nothing held. On iPhone, windows shorter than fifteen minutes, which can happen far north in summer, are skipped rather than flashing on and off.
On iPhone: Apple’s Screen Time framework
On iPhone, the Shield is built on Apple’s Screen Time API, the same framework behind Apple’s own app limits. It has four parts.
Your permission. During setup, Awwab asks iOS for permission to use Screen Time for yourself. This is Apple’s “individual” authorization, introduced in iOS 16 so that people can manage their own phone rather than a child’s. You can skip it and set it up later from the Home screen, and you can withdraw it at any time in the iPhone’s Settings.
Your choice of apps. You pick apps, or whole categories, in Apple’s own picker. iOS gives Awwab back tokens: opaque references that the system can act on but that don’t tell the app which apps they stand for. Awwab can ask iOS to hold “these tokens” at prayer time, but it can’t read their names, and the selection stays on your iPhone. It isn’t synced to iCloud.
The schedule. Awwab registers each prayer window with iOS. When a prayer time begins, iOS briefly wakes a small part of Awwab in the background, even if you haven’t opened the app all day. It checks whether that prayer is already marked, applies the Shield if not, and sends a single notification that the prayer’s time has come.
The Shield screen. When you open a held app, iOS shows Awwab’s shield screen in its place: the name of the prayer, a verse, and the two buttons, in the same language as the app.
On Android: Usage access and an on-device overlay
Android has no Screen Time framework that apps can use in the same way, so the Android Shield works differently, and it is just as local.
- Two permissions. It needs Usage access, which lets it see which app is in front, and Display over other apps, which lets it draw the prayer screen on top. Android shows a small ongoing notification while the Shield is on.
- A check every second. While the Shield is on, it looks at which app is open. If it is one you chose, and the current prayer hasn’t been marked, it covers the app with the full-screen prayer reminder, with the same verse and two buttons. The check happens in the phone’s memory and isn’t saved or sent anywhere.
- No accessibility tricks. The Android Shield doesn’t use the accessibility service that some blockers rely on. It uses the overlay instead, which asks for less access to what is on your screen.
- Local-only. The Android app has no Awwab cloud at all. The list of apps the Shield holds is stored on the phone, and, like your other settings, it is part of your own Google backup if you have backup turned on.
The phone is not the enemy. It just shouldn’t get to answer the adhān before you do.
“Go to prayer”
This is the main button, and on both platforms it leads to the same place: a calm screen in Awwab that opens on the qibla and a short duʿāʾ, ready for you to pray and mark the prayer.
On Android, the button opens Awwab directly. On iPhone, Apple doesn’t allow a shield screen to open another app, so tapping it sends you a notification instead; tap that, and Awwab opens on the prayer. If you already marked the prayer, for example on the Home Screen widget, the button notices and simply lets you in.
“I have a reason”
Life doesn’t stop for a timetable. A school calls, a delivery driver is lost, a colleague needs one answer now. The second button lets you through, for a few minutes you set yourself: three by default, anywhere from one to thirty.
- Only what you tapped is lifted. On iPhone, if you picked an app as part of a whole category, iOS lifts that category for the pause. On Android, only the one app under the overlay is lifted.
- When the minutes are up, the Shield comes back, and a quiet notification tells you so.
- In Settings you choose how many times per prayer the Shield returns after a pause: never, once, twice, three times or always. Once is the default.
- When that allowance is used up, the apps you let through stay open for the rest of that prayer’s window. The Shield doesn’t argue with you, and the prayer is still waiting.
On Android the pause is measured on the phone’s internal clock, so changing the time in Settings can’t stretch it.
“I prayed”: how the Shield lifts
The Shield lifts in one way only: when you mark the prayer as prayed. You can do that in the app, after the prayer screen, or on iPhone straight from the Home Screen widget. Everything unlocks at once, and any pause still running is cancelled.
A window is never released just because time passed. If you don’t mark ʿAṣr, the Shield stays on through ʿAṣr. But when Maghrib begins, it moves to Maghrib: it doesn’t pile missed prayers on top of each other or lock your phone for the rest of the day. If a prayer did slip by, our guide to making up missed prayers explains what to do, gently.
Two cases switch the Shield off by design. If you track your cycle in Awwab and a period is logged, the prayers are excused and the Shield rests until it ends. And if you haven’t picked any apps, there is nothing to hold.
What the Shield never sees
- On iPhone, Awwab can’t see the names of the apps you chose, only Apple’s opaque tokens. The phone-use summary in the app is drawn by Apple inside its own protected view, so the numbers never pass through Awwab’s code.
- On Android, the Shield reads which app is in front, second by second, to decide whether to show the overlay. It doesn’t keep a history, and nothing leaves the phone.
- On both, there is no account, no analytics and no server of ours. We can’t know whether you prayed, which apps you hold, or how often you tap “I have a reason”. More in Private by design.
Honest limits
The Shield is a commitment you make to yourself, not a lock someone else holds. That is deliberate, and it comes with limits worth knowing:
- You can always switch it off. On iPhone you can withdraw Screen Time permission in Settings; on Android you can turn off Usage access or the overlay. Awwab notices on iPhone the next time you open the app and offers to set it up again.
- Websites aren’t held. On iPhone the Shield holds apps and app categories, not websites in a browser.
- Android phones differ. Some manufacturers stop background services aggressively to save battery. If that happens, Awwab shows a notice that the Shield is paused, and opening Awwab switches it back on. Allowing Awwab to run in the background in your battery settings helps.
- Times depend on your location. Awwab updates your location when you open it. If you travel to a new time zone while the app is closed, it asks you to open it so the times are right.
- It isn’t a parental-control tool. On iPhone it is set up with individual authorization, for your own phone.
A tool, not the reason
A Shield can stop you opening an app. It can’t give you the reason to stand on the prayer mat; that comes from knowing who you pray to and why. Sūrat al-Jumuʿah describes the pattern well: when the call comes, leave the trade in your hands, and when the prayer is done, go back out and seek God’s bounty (Qur’an 62:9–10). The Shield helps with the first half of that verse. The rest is yours. And be gentle with yourself while you build the habit: the deeds God loves most are the most consistent, even if small (Ṣaḥīḥ al-Bukhārī 6464, Ṣaḥīḥ Muslim 783). For more on attention and prayer, read Your phone and your prayer.
Frequently asked questions
Can Awwab see which apps I block?
On iPhone, no. Apple gives Awwab opaque tokens for the apps you pick, and the app can apply the Shield to them without learning their names. On Android, the list of chosen apps is stored only on your phone (and in your own Google backup if you use it), and nothing is sent to us.
What happens if I don’t mark a prayer as prayed?
The Shield stays on for that prayer’s window. When the next prayer begins, it moves to that prayer instead. It never stacks missed prayers or locks your phone for the rest of the day.
Does the Shield work when Awwab is closed?
Yes. On iPhone, iOS wakes a small part of Awwab at each prayer time even when the app is closed. On Android, the Shield runs as a background service with an ongoing notification while it is on.
Can I get into an app in an emergency?
Yes. Tap “I have a reason” and the app opens for the minutes you set, three by default. You also choose how many times per prayer the Shield returns afterwards. You are never trapped.
Sources
Qur’an references open the verse on quran.com and hadith references open the narration on sunnah.com, where you can read the full text. Narrations in Ṣaḥīḥ al-Bukhārī and Ṣaḥīḥ Muslim are accepted as authentic by the scholars of hadith; for other collections the grading is given beside the reference.
- Qur’an 4:103: prayer decreed at specified times.
- Qur’an 62:9–10: leave trade at the call, and seek God’s bounty after the prayer.
- Ṣaḥīḥ al-Bukhārī 527 and Ṣaḥīḥ Muslim 85: prayer at its time, the deed God loves most.
- Ṣaḥīḥ al-Bukhārī 6464 and Ṣaḥīḥ Muslim 783: the most consistent deeds, even if small.
- Apple Developer, Family Controls, authorization and the app picker.
- Apple Developer, FamilyActivityPicker, choosing apps and categories.
- Apple Developer, Managed Settings, applying a shield to app and category tokens.
- Apple Developer, ShieldConfigurationDataSource, the custom shield screen.
- Apple Developer, ShieldActionDelegate, handling the shield’s buttons.
- Apple Developer, DeviceActivityMonitor, background callbacks at scheduled times.
- WWDC21, Meet the Screen Time API, opaque tokens that represent apps and websites.
- WWDC22, What’s new in Screen Time API, individual authorization from iOS 16.
- Android Developers, UsageStatsManager, reading which app is in front, with Usage access.
- Android Developers, SYSTEM_ALERT_WINDOW, the “Display over other apps” permission.
- Android Developers, Foreground service types, services that run with an ongoing notification.
- Awwab Privacy Policy, what the Shield stores on each platform.