Four ways a blocker can work, and only one reaches the app
A phone can be made to refuse a bookmaker in four ways, and every product is one or more of them.
- A DNS answer points the phone at a resolver that will not return an address for a name on its list.
- A VPN profile routes the traffic through a filter running on the device.
- A Safari content blocker refuses addresses inside Safari and inside the browser Apple embeds in other apps.
- A Screen Time shield is Apple's own restriction system, driven by an installed app, holding the seal in the operating system.
Three of those four work on traffic. Only the fourth works on the app. That is the whole distinction: a resolver can starve a betting app of every byte it wants and the icon still opens, still loads its shell, still remembers who you are. The dated comparison of the four mechanisms sets out what each one reaches and what it leaves open, in one table, with no other product named. This post is about what that table does not cover: why the category is so lopsided in the first place.
The one capability that reaches the app has a gate in front of it
The Screen Time shield is exposed to developers as the Family Controls framework. Apple describes the framework's purpose in one line on its Family Controls documentation, Authorize your app to provide parental controls on a device, and an app granted it can seal chosen apps, seal a whole App Store category, filter website addresses inside Safari and refuse app deletion across the device.
You cannot simply write that code and ship it. Apple's own page Requesting the Family Controls entitlement, read on 10 September 2026, opens with the requirement: Before you distribute an app that uses Family Controls, your Apple Developer Account Holder must request permission to use the com.apple.developer.family-controls entitlement, and update your Xcode project to use the entitlement.
One of the apps holding that entitlement is Fold'em, which uses it to seal the betting app itself and makes ending that protection a request that takes days. That is a statement about plumbing and not about quality, and the rest of this page is why the distinction decides so much.
Three details on that same page decide how heavy the gate is. It is a request to Apple, made at a single form. It has to be made again for each Screen Time extension an app ships, and Apple names them: Device Activity Monitor, Device Activity Report, Shield Action, or Shield Configuration. And the answer is a review rather than a registration, in Apple's words Apple reviews your app, and if it's approved, adds the entitlement to your developer account using managed capabilities. Apple's capability requests help page adds who may ask, Required role: Account Holder, and neither page names a timescale for the answer.
One thing worth saying plainly, because it is easy to write around. The form itself is not public. Requested on 10 September 2026, the address above returns a redirect to Apple's account sign in page rather than a form, so what a developer types into it is not something a reader can go and check. Nothing on this page is quoted from it. The documentation around it is quotable, and that is what is quoted here.
What that single gate explains
Put the two halves together. The only mechanism that stops a native app from opening needs a permission one company has to ask another company for, per app, per extension, in the account holder's name. The other three mechanisms need nobody's permission at all. A DNS profile, a VPN profile and a Safari content blocker can each be built, shipped and updated without asking Apple for anything beyond the ordinary App Store review.
So a great deal of what is sold as gambling blocking on iOS is a resolver, a profile or a Safari extension. Those products are not lying when they say they block gambling. They block gambling traffic, a DNS or VPN profile in every browser and a Safari blocker in Safari. The betting app still opens. Some say so on their own pages, in a sentence near the bottom that a reader has no reason to notice matters.
It is worth naming the capability rather than admiring it. Apple did not build a good blocker and a bad one. It built one narrow tool for parental controls, put a request in front of it, and the market arranged itself around the request.
Apple approves a capability, and never a product
This is the part that would be convenient to leave out. Holding the Family Controls entitlement means Apple agreed an app may use a parental controls capability. It is not a finding that the app is honest, that it is well built, that it is effective against a gambling habit, or that it is hard to get around. Nothing in Apple's process assesses any of that, and none of those claims is Apple's to make. Apple publishes no register of which apps hold the entitlement either, so a reader cannot verify any product's claim to hold it, and that includes ours: the status appears in the developer's own account, not on a public list. And the capability changes nothing about the fact that the Screen Time permission behind it belongs to the person holding the phone and can be withdrawn in iOS Settings at any time, by anyone who can unlock that phone. No app on iOS can prevent that, ours included. What a good arrangement buys is time, a record and another person, never prevention.
The test you can run yourself, and it is two minutes
None of this needs to be taken on trust. The difference is visible on your own phone, and the test is one line: try the app, not the website.
- Install the blocker you are considering and set it up the way it asks, with gambling turned on.
- Open a betting app that is already on the phone. Not its website. The app.
- Watch the icon. If the app opens at all, even to an error or an empty screen, the product is working on traffic and not on the app. If the app refuses to open and the phone shows a blocking screen over it, the product is using the Screen Time shield.
- Then open the same bookmaker in Safari, and again in a second browser you have installed. A Safari only product will cover the first and miss the second.
One habit settles most of the rest without trusting any page, this one included: look on the product's own site for the word that names its mechanism, because DNS, VPN, content blocker and Screen Time are ordinary words a product that uses one is free to print.
What the gate does not touch
The entitlement is a developer gate, and developer gates do not reach the person using the phone. Screen Time permission is granted by you and withdrawn by you, which is the honest ceiling in this category and the reason what Screen Time does on its own is worth reading first. If you set your own Screen Time passcode, you can lift your own restrictions, and Apple's support page If you forgot the Screen Time passcode for an iPhone or iPad sets out the recovery route: the passcode can be reset with the Apple Account that was used to set it up. Handing somebody a four digit number while keeping that Apple Account yourself is a gesture, not a lock. Source: Apple, if you forgot the Screen Time passcode, read 10 September 2026.
What a blocker can genuinely change is what stands between the urge and the bet: how many seconds it takes, whether the undo is on the phone or somewhere else, and whether anybody else knows. That is a different question from which mechanism it runs on, and why blockers fail separates the failures that belong to the tool from the ones that follow you to the next tool. The mechanism question is only the one you can settle in two minutes.
