Why I Built an App With No Bypass Button

Every screen time app on the market has a bypass button. Every single one.

Apple Screen Time has "Ignore Limit." Opal has session cancellation. Freedom lets you end sessions. One Sec lets you tap through. The entire category is built on the same assumption: give users the option to override their own restrictions.

This assumption is wrong. And it is the reason most people fail at fixing their phone habits.

The Override Paradox

Here is the logic that every other app uses: "We should give users control. What if they need to access a blocked app? We cannot lock them out completely — that would be too aggressive."

Sounds reasonable. It is also the exact reason these products do not work.

The person setting up the app blocker at 3 PM is a different person than the one lying in bed at midnight. The 3 PM version is rational, well-rested, and genuinely committed to better sleep. The midnight version is dopamine-depleted, willpower-exhausted, and physically incapable of resisting the "Ignore Limit" button that is one tap away.

You are not designing for one user. You are designing for two users who share the same body. The daytime user sets the rules. The nighttime user breaks them. Every bypass button is a concession to the nighttime user — and the nighttime user will always, always use it.

I know this because I was that user. I tapped "Ignore Limit" on my own Screen Time restrictions every single night for months. I would set limits during the day with genuine conviction. By midnight, I had undone every single one. The conviction was real. The follow-through was impossible. Not because I was weak — because the product was designed to let me fail.

The Insight That Changed Everything

The realization was simple: the bypass button is not a feature. It is a bug.

Every other screen time app treats the override as a safety valve. "What if the user really needs access?" But in practice, the override is used in exactly one scenario: the user wants to keep scrolling and their depleted brain finds the easiest path to do so.

I looked at my own Screen Time data. I had set limits on Instagram, TikTok, Reddit, and Twitter. Over 60 days, I had overridden those limits on 57 of them. The three days I did not override? Two were days my phone died early, and one was a day I fell asleep before the limit hit.

The data was clear. The bypass was not a safety valve. It was an escape hatch that I used every time it was available.

So I removed it.

What Happens When You Remove the Escape Hatch

When we built Sunbreak, the first and most important product decision was: no bypass button. When your apps lock at bedtime, they stay locked until sunrise. Period.

People told me this was too aggressive. "Users will hate it." "You need an override for emergencies." "Nobody wants to be locked out of their own phone."

They were wrong on all three counts.

Users do not hate it. They are relieved. The number one piece of feedback we get is some version of "thank god I cannot override this." People are tired of fighting themselves every night. Removing the fight is not aggressive — it is merciful.

Emergencies are a red herring. Your phone still works. Calls, texts, alarms — all functional. The "emergency" people imagine is never "I need to call 911 but my phone is locked." It is "I want to open TikTok at midnight and I am telling myself it is urgent." Those are not the same thing. We do offer one emergency unlock per week — 15 minutes, then it locks again. Most users never use it.

People do want to be locked out of their own phone. That is literally why they download the app. They are looking for the version of themselves that will not cave at midnight. Sunbreak is that version, automated.

The Willpower Tax

Here is a framework for thinking about this.

Every app with a bypass button imposes a willpower tax. Each time the override prompt appears, the user has to spend willpower to resist it. The tax is small in isolation — one decision, one tap to dismiss. But willpower is a finite resource, and it is at its lowest at night.

Stack that tax across every night, every limit notification, every "Ignore for 15 minutes?" prompt, and you are asking a depleted brain to make the right choice hundreds of times per month. The math does not work. You will fail eventually. Probably tonight.

Removing the bypass button reduces the willpower tax to zero. There is no decision to make. There is no prompt to resist. The apps are locked. You read a book, you do some breathing exercises, you fall asleep. The entire nightly negotiation disappears.

The best product decisions are the ones that remove decisions from the user.

The Counterargument, and Why It Is Wrong

The strongest counterargument is autonomy. "Users should be in control of their own devices." I agree — and they are. They choose to install Sunbreak. They choose their bedtime. They choose which apps to block. They make every decision during the day, when they are capable of making good decisions.

What they are choosing is to pre-commit. To bind their future self. This is not a loss of autonomy — it is the most sophisticated exercise of it. Odysseus tied himself to the mast not because he was weak, but because he understood what the Sirens would do to his decision-making. The ropes were not a constraint on his freedom. They were the expression of it.

Every Sunbreak user is tying themselves to the mast. The app is the rope. And the Sirens are TikTok at 1 AM.

The Results

Since launch, the data has confirmed the thesis:

Users who stick with Sunbreak for a week report falling asleep 30-45 minutes faster. Their bypass attempt rate drops from high in the first few days to near-zero by the end of the first week. Not because they stopped wanting to scroll — because they stopped trying. The absence of an escape hatch rewires the habit faster than any amount of willpower training.

The no-bypass design is not a limitation. It is the entire product. Everything else — the sunrise unlock, the wind-down routine, the accountability partners — is built on the foundation that when your apps lock, they stay locked.

If you could override it, none of the other features would matter.

The Takeaway

If you are building anything in the behavior change space, here is the lesson: do not design for the user's best self. Design for their worst self. The best self does not need your product. The worst self — tired, depleted, irrational — is the one who will interact with it at the critical moment.

Every bypass button, every "are you sure?" dialog, every override option is a bet that the worst self will make the right choice. That bet loses every time.

Remove the bypass. Remove the decision. Let the user set the rules when they are strong, and enforce them when they are not.

That is the entire philosophy of Sunbreak. And based on the data, it works.