Why blocking Candy Crush specifically
Candy Crush looks like a casual puzzle game. It plays like one too, at least in the first few levels. What distinguishes it from a crossword or Sudoku is the mechanics underneath the surface: a lives system that empties after five failures, then slowly refills over time. When your lives are full, the game fires a push notification to tell you. That notification is not a reminder -- it is a re-engagement hook engineered to pull you back at the exact moment your ability to play is restored.
Combine the refill notification with near-miss level design (you can see exactly how close you came to beating the level before running out of moves), sunk-cost progression (you are on level 4,000 and you have been playing for two years), and optional in-app purchases that let you buy your way past a hard level, and you have a loop that does not rely on quality of content. You do not keep playing because the game is good. You keep playing because stopping feels like leaving something on the table.
One meaningful difference from feed-based apps like TikTok or Instagram: Candy Crush does not have a web fallback. There is no browser version you can drift to when the app is gone. That makes deletion genuinely effective here in a way it is not for feed apps. This guide accounts for that -- deletion is ranked higher and recommended more strongly than in guides for social media apps.
Method 1: Turn off Candy Crush notifications
How: Settings > Notifications > scroll to Candy Crush Saga (and Candy Crush Soda Saga, Candy Crush Jelly Saga, or whichever variants you have installed) > Allow Notifications > toggle off. Do this for every Candy Crush title on your phone.
Strength: 6/10. This does not block the app. You can still open it whenever you want. But you remove the primary re-engagement mechanism: the lives-refilled ping. Without the notification pulling you back, the app has to rely on habit and boredom alone. For many people, that is enough to break the loop -- the game was never that compelling on its own merits, only after being summoned.
When to use: always, and first, before any other method. Even if you plan to keep playing occasionally, removing the notification means you play on your terms rather than the game's. If you want to play, you open it intentionally. The game stops interrupting your day. This is the cheapest intervention with the highest return and there is almost no reason not to do it.
Method 2: App Limit
How: Settings > Screen Time > App Limits > Add Limit > (uncheck all) > expand "Games" > find and check Candy Crush Saga (repeat for each variant) > Next > set a daily time limit (5 or 15 minutes) > Add.
Strength: 2/10 without a passcode, 7/10 with one. The "Ignore Limit For Today" button is one tap and it ends the block for the rest of the day. Without friction on that button, this method is an alarm you can snooze indefinitely.
When to use: combine with Method 1 (notifications off) as a first attempt. Think of the App Limit as an audit tool -- it tells you how many times per day you were about to open Candy Crush out of habit and the lock stopped you. If you ignore the limit within the first 48 hours, you have learned that soft limits do not hold for you and can escalate to Method 3.
Method 3: Screen Time passcode
How: Settings > Screen Time > Use Screen Time Passcode > set a 4-digit code that is different from your iPhone unlock code. Then apply the App Limit from Method 2. Now bypassing the limit requires entering a passcode you have chosen not to memorize.
Strength: 5/10 if you know the passcode and 9/10 if you do not. The realistic version of "do not know it": ask a partner, parent, sibling, or friend to set the passcode on your behalf and not tell you what it is. They hold the override. You play only if you call them and ask -- which adds enough friction and social accountability that most people do not bother.
When to use: when Method 2 alone has failed within a week. The passcode-held-by-someone-else is one of the cheapest hard commitment devices available. No apps to download, no money involved -- just a relationship with someone who will not hand the code over when you ask during a low-willpower moment at 11pm.
Method 4: Delete the app
How: Hold the Candy Crush icon > Remove App > Delete App. Repeat for every Candy Crush variant installed. Your level progress is saved server-side; you can always recover it by reinstalling and signing back in to your account.
Strength: 4/10 on its own, higher than deletion for feed apps because there is no web version to drift to. The App Store re-download takes 30 seconds, so the mechanism is pure friction. But friction alone does not survive a strong urge. What it does do is remove the idle-habit open -- the absent-minded tap when you are bored.
Important note on progression: the sunk-cost feeling around your level count is real, but your progress is not at risk. Deleting the app does not delete your save. When (if) you decide to reinstall, you pick up where you left off. This removes the loss-aversion argument that often keeps people from deleting -- there is genuinely nothing to lose by trying a week without it.
When to use: as a 7-day experiment. Delete it tonight. If after a week you do not miss it, keep it gone. If you reinstall within 48 hours, the habit is stronger than simple deletion handles, and you should escalate. Unlike TikTok or Instagram, Candy Crush has no web substitute to fill the gap, which makes the experiment cleaner -- absence is actually absence here.
Method 5: Add a verified-exercise consequence
How: Set a daily phone-time limit in iOS Screen Time (for example, 45 minutes across all games or all apps). Install ScreenFine ($1/week subscription). When you go over your daily limit, ScreenFine tracks the overage and requires 25 pushups per 15-minute block before the fine clears. Time spent in Candy Crush counts toward your daily total.
Strength: 8/10. The consequence is real -- your body does the pushups or the fine sits on the record. The user can pause the jar at any time (the autonomy escape hatch), which is a deliberate decision rather than a tap-through bypass, so it does not collapse to willpower the way "Ignore Limit" does.
The mechanics here match the problem. Candy Crush exploits the same psychology as near-miss gambling: the cost of one more session feels small until you look up and it is been an hour. Attaching a physical cost per overage block makes that cost visible and immediate rather than abstract and deferred. Loss aversion -- the same force that makes you want to finish a nearly-beaten level -- now works in your favor.
When to use: when Methods 1-4 have failed and you need a structural commitment device. Also effective when the problem is not a single app but total daily phone time, with Candy Crush as the main contributor. See the loss aversion guide for the underlying mechanism, and commitment devices for why soft intention-based methods systematically fail under habit patterns.
Which method should you pick?
- Always start here: Method 1 (notifications off). Costs nothing. Removes the primary re-engagement hook. Do this regardless of which other method you choose.
- First attempt at limiting play time: Method 2 (App Limit, no passcode). Audit phase -- see what happens in the first 48 hours.
- If Method 2 fails within a week: Method 3 (passcode held by someone else). Cheapest escalation with real friction.
- If you want a clean break: Method 4 (delete). The 7-day experiment. Progress is saved server-side, so there is no sunk cost to protect. Deletion is more effective for Candy Crush than for feed apps because there is no web fallback.
- If 1-4 have all failed: Method 5 (verified-exercise consequence). Hard commitment device, body cost per overage block.
One pattern worth naming: a lot of Candy Crush overuse is not driven by the game itself but by the notification loop. People who would never seek the app out deliberately find themselves opening it immediately after the lives-refill ping. If that sounds accurate, Method 1 alone -- notifications off -- may solve the whole problem without needing anything else.
The honest read: the hardest cases are users who are deeply embedded in the sunk-cost of long level progressions and who have a long-standing idle-habit pattern around the app. For them, soft methods (1-3) may slow things down but rarely eliminate the behavior. Method 4 (deletion) works well here because the game genuinely has no web alternative -- but only if the person can resist reinstalling during the first 72 hours, which is when the urge is highest. Method 5 adds the structural cost that covers the gap when willpower alone does not.