Comparison · 9 min read

Opal vs Brick vs doing something entirely different

Two good answers to one question (how to restrict access), and a third mechanism that never gets on the chart.

If you’ve landed on this comparison, you’ve probably already narrowed the field to two shapes of the same idea. Opal is software that blocks apps. Brick is a piece of hardware that locks them. Both are well-made, both have real fans, and the usual write-up pits them against each other on how hard each is to bypass. That’s a fair fight, and we’ll have it below.

But it’s worth noticing what the fight assumes. Both of these tools do the same fundamental thing: they restrict access. They stand between you and the app and make getting in harder. The whole Opal-vs-Brick debate is an argument about how to build that wall: in software you can reschedule, or in hardware you have to physically tap. It’s a good argument. It just isn’t the only axis, and if you’ve bounced off blockers before, the axis you’re missing might be the one that matters.

So this is a comparison in two parts. First, an honest head-to-head between Opal and Brick on the thing they actually share, restricting access, because for some goals that is exactly the right mechanism and one of them is clearly better for you. Then a third option that isn’t on the chart at all, because it doesn’t restrict access. It drains the reward instead. Nothing to bypass, because nothing is blocked.

Opal: the flexible software block

Opal is built on Apple’s Screen Time API, the same machinery iOS uses for its own app limits, exposed to a third-party app with a much better interface wrapped around it. You group your distracting apps, set schedules, and Opal enforces them: shields appear, sessions get gated, and “Deep Focus” mode raises the difficulty of talking your way back in. At the time of writing it runs on iOS and Android, free with a paid tier sold as a subscription. Prices and ratings drift; the mechanism doesn’t.

What Opal is genuinely good at: flexibility. It’s always on, always with you, and it costs nothing to carry because it’s already living in your phone. You can schedule a workday block, a bedtime block, a weekend loosening, all without touching a physical object. For someone who wants an intelligent, always-present guardrail, it’s a strong pick.

The honest limitation is structural, and it’s the same one every software block shares: the block is made of software, and you are the administrator. When the shield appears at 11pm, the path back in is a few taps through a menu you configured, and at 11pm the version of you that wants the app is more motivated than the version of you that set the limit that morning. Opal makes that path deliberately inconvenient. It does not make it impossible, because it can’t; the phone answers to you, and a wall you can reschedule is a wall you can argue with. For a lot of people that’s fine. For some, it’s the exact loop they came here to escape.

Brick: the physical commitment device

Brick answers that limitation by leaving the phone entirely. It’s a small, battery-free NFC puck (you stick it to a wall or a desk), paired with an app. Tap your phone to the Brick and your chosen app groups lock; the only way to unlock them is to physically tap the Brick again. At the time of writing it’s a free app plus a one-time hardware purchase, with no subscription, and it works on iOS 17+ and Android 12+.

The design is doing something clever. By moving the unlock into the physical world, Brick converts “a few taps in a menu” into “get up, walk to where the puck is, and tap it.” If you leave the house without the Brick, or leave it in another room on purpose, the apps stay locked and there’s genuinely no software back door to find, because the gate isn’t software you administer, it’s an object you’re not near. That’s a commitment device in the classic sense: you bind your future self by making the escape hatch inconvenient in a way willpower alone can’t undo.

The tradeoff is the flip side of the same coin. Brick is deliberately less flexible. That’s the point, and pretending otherwise would miss what it’s for. It costs money up front, it’s a thing you have to carry or deliberately leave behind, and the friction that makes it effective is friction you feel every time. For total abstinence from an app, or a genuinely hard commitment you don’t trust yourself to keep, that inconvenience is a feature. It is the most physically honest block in this comparison, and if a real wall is what you need, it’s probably the wall to buy.

Same axis, two good answers

Line them up and the choice is clean, because they’re answering the same question differently:

• Opal: software, always-on, flexible, a subscription. The block is real but it’s software you can talk yourself past. Best when you want a smart, ever-present guardrail and you’re mostly disciplined.
• Brick: hardware, high-commitment, a one-time cost, deliberately inconvenient. The block is genuinely harder to bypass because it’s physical. Best when you want abstinence or a firm commitment and “inconvenient” is exactly what you’re buying.

Neither of these is a bad tool. If your goal is a hard deadline this week, or total abstinence from a specific app, or a commitment you want to physically bind yourself to, a real block is the right shape, and between these two, pick Opal for flexibility and Brick for firmness. That’s the actual answer to “Opal vs Brick,” and for a lot of people it’s the end of the search.

But both answers live on one axis: restrict access, harder or softer. Here’s the other axis.

The entirely different thing: drain the reward, don’t block the access

There’s a third mechanism that neither Opal nor Brick uses, and it inverts the whole premise. Instead of standing between you and the app, it leaves the app wide open, and makes the app itself less rewarding to be in. That’s de-stimulation, and the cleanest form of it is grayscale: strip the color out of a feed and you strip out the saturated reds, the story rings, the vivid thumbnails that are engineered to catch your eye pre-consciously. The app still opens instantly. There’s just less payout waiting inside.

Notice what disappears. There’s no shield, so nothing to tap through. There’s no lock, so nothing to walk over and unlock. There’s no override, because there is nothing to override, and no argument between morning-you and midnight-you, because no wall was ever built for midnight-you to knock down. Access was never the battleground. The appetite was.

And the evidence here is unusually tidy for a wellbeing intervention. Across published field studies, running a phone in grayscale reduces objectively measured screen time (logged by the device, not self-reported) by roughly 20 to 40 minutes a day^{1 2 3}, a range that holds across different countries, samples, and study designs.

The detail that matters most for this comparison comes from Dekker and Baumgartner (2024, Mobile Media & Communication): across two weeks with 84 participants, grayscale cut daily screen time by about 20 minutes while the number of daily phone unlocks didn’t change at all². Read that carefully, because it’s the exact inverse of a blocker. You still reach for the phone just as often (the habit loop is untouched), but you put it down sooner, because there’s less holding you there. Opal and Brick work by stopping the reach. Grayscale leaves the reach alone and shrinks the session. Zimmermann and Sobolev’s pre-registered 2023 experiment (Cyberpsychology, Behavior, and Social Networking, N = 112) put grayscale and self-set time limits against a self-monitoring control: grayscale produced an immediate, significant reduction, and time limits a smaller, more gradual one¹. Holte and Ferraro’s 2020 “True colors” study (The Social Science Journal) found college students cut screen time by 37.90 minutes a day, and (the reading that gives the whole approach its logic) concluded that grayscale makes smartphones less gratifying³. Nobody stopped them. The phone just stopped paying out.

This isn’t a claim that grayscale beats a blocker at the blocker’s own job. If you need total abstinence or a hard physical commitment, it doesn’t. Buy the Brick. De-stimulation is a different job: sustainable, all-day moderation for an app you intend to keep using, without a wall you’ll spend every evening arguing with.

Where Dwindle fits

Doing grayscale the manual way means turning your whole phone gray through iOS system settings (camera, photos, everything), which is exactly the all-or-nothing tradeoff that drives people to abandon it. Dwindle does the per-app version instead: your feeds go gray, your camera and photos stay in full color, automatically. No major app ships per-app grayscale natively, which is the gap it fills. Nothing is blocked, nothing is shielded, there’s no schedule to defeat and no puck to carry. The app opens exactly as fast as it always did. It just stops paying out.

That’s the third axis nobody puts on the Opal-vs-Brick chart. If a wall is what you need, one of those two is your answer, and honestly so. If what you actually want is to reach for the phone less often without fighting yourself every time you unlock it, that’s a different mechanism, and it’s the one Dwindle is built on.

Related guides: why de-stimulation beats blocking, the one sec review, ScreenZen vs one sec vs Dwindle, and the science of grayscale.