Block Chrome itself or selected websites on iPhone?

The practical answer

Blocking the Chrome app and blocking a website inside Chrome are different selections. Lesscue supports Chrome app-level boundaries on iOS 17 and later. Its website compatibility contract covers Safari on iOS 17+ and the WebKit integration route for Chrome on iOS 26+; it does not promise every browser configuration behaves identically.

A setup to try

1. Decide whether your task needs Chrome at all. If it does not, select the Chrome app as an app boundary rather than trying to enumerate every distracting website.
2. If you need a browser for work, select supported website domains separately and keep essential research destinations available. Record the iOS and browser versions you are actually using.
3. Test the specific route you normally use: a normal tab, a link opened from another app, and any alternate browser. A successful app-level block does not establish domain-level coverage.
4. If your Chrome and iOS combination falls outside the website support matrix, use an app-level boundary or Safari for the planned session. Do not describe an untested route as fully protected.

Can Lesscue block the whole Chrome app on an older iPhone?

Chrome can be selected as an application in Apple’s Screen Time picker on Lesscue’s supported iOS versions, starting at iOS 17. This is a whole-app boundary. It does not require Chrome to expose each website visited inside the browser to Lesscue.

Can I block reddit.com in Chrome while leaving other Chrome tabs usable?

That is a website-level request, so the browser and iOS version matter. Lesscue’s stated route is WebKit-based Chrome on iOS 26 or later with a selected website policy. Test the exact domain and browser build before relying on selective access for a work session.

Why does a Chrome app block work while one website still opens in Safari?

The Chrome application token and a website domain token are separate selections. Blocking Chrome does not automatically select the same destinations in Safari. Add the distracting website through Apple’s picker if it is available, then verify the Safari route independently.

Does Always Allowed Chrome also allow every blocked website inside it?

No. Lesscue’s Always Allowed model applies to selected individual apps; it does not erase a separate domain policy. Allowing the browser can preserve access to useful sites while selected website boundaries remain relevant in supported browser configurations. Check both selections when reviewing a group.

Does Lesscue guarantee website blocking in Chrome on iOS 18?

No. Specific-domain blocking in Chrome on iOS 17 or 18 is outside Lesscue’s supported website matrix. You can instead select Chrome as an app boundary or use a supported Safari website setup. Do not treat the newer WebKit integration as proof about older iOS behavior.

Does this also block Chrome on my Mac or Windows laptop?

No. Lesscue is an iPhone app, and its local Screen Time setup does not install a desktop browser extension or a computer-wide filter. If the same distraction is available on your laptop, define a separate desktop boundary before describing the whole task as covered.

What if a link opens in the browser built into another iPhone app?

An embedded browser is a separate route to test. iOS 26 adds a WebKit Screen Time integration path, but apps can use different configurations or engines. Lesscue does not promise every in-app browser is covered merely because a Safari test passed.

Can I use a different browser engine and expect the same website policy?

Do not assume that. Website enforcement depends on the engine’s integration with Apple’s Screen Time mechanisms. Lesscue’s compatibility statement is version- and engine-specific. Selecting the browser application itself remains a different option when a selective website route is outside the supported matrix.

Does seeing Chrome in Insights prove each Chrome website was recorded?

No. A browser application total does not prove a complete domain breakdown exists. Browser reporting and website enforcement use related but distinct system paths. Read the actual domains Apple supplies in the report, and treat a missing domain as unavailable data rather than a zero-use result.

What details should I include when reporting a website that still opens?

Include the iOS version, browser version, whether the app or domain was selected, and the route you used to open it. Avoid sending browsing history or account credentials. Those details distinguish a selection issue from an unsupported engine or a specific compatibility failure.