How Apple’s Push Notifications Undermine Mindfulness
14 min read
Last tended to: 1 minute ago

I’ve been tinkering with different ways to manage my smartphone usage for years now. I’ve tried minimalistic launchers (back when I had a bunch of Android phones), auto-set my phone to greyscale at night to quell the dopamine rush of bright icons, and tested just about every note-taking app on the planet. Yet somehow, no matter how many times I vow not to be overrun by my phone, Apple’s iOS push notifications still find a way to make me feel like I’m an on-call nurse for the entire internet. The prime suspect, in my view, is Apple’s own push notification service—winding its serpentine tail through every app, every corner of the operating system, every little beep that lights up the screen.
I came to a realization recently: technology has been meticulously shaping how we think we should be available. Don’t get me wrong; Apple’s ecosystem has some lovely aspects. I enjoy iMessage on my Mac, and AirDrop is a near-miraculous solution for sharing photos or files. But the moment you decide, “Wait, I’d like to be less constantly reachable,” iOS stands firm, crossing its arms with that paternalistic Apple vibe: “We know better.”
The impetus for me writing this is a change I recently made in my life:: turning off mobile data for all my chat and social media apps. In other words, these apps will only connect when I’m on Wi-Fi. I shared this plan with friends and family, letting them know I won’t be reachable on WhatsApp et all while out and about. The phone number is still there for actual calls and SMS—so if it’s urgent, they know what to do.
Why am I doing this? Partly it’s about boundaries—this idea that I don’t need to carry an “always on” communications device in my pocket. That I can be present in the moment, or, put differently, less anxious about who might be trying to reach me. It sounds nice in theory, but then iOS’s labyrinthine settings come into play. Did you know that while you can disable cellular data for each individual app, Apple doesn’t allow you to tie that specifically to when you want to receive notifications or not? This means I can block WhatsApp from using cellular data, but notifications for that app still buzz me—pointless pings about messages I can’t read until I connect to Wi-Fi. Doesn’t that defeat the purpose?
And so began my quest to find a solution.

I discovered early on that Apple’s Focus modes can allow or block notifications from certain apps. You create a “Focus,” say “Wi-Fi Only,” which could in theory hide notifications from any chat app you do not want to hear from unless you’re connected to Wi-Fi. But—and here is the crucial catch—Focus modes don’t know (and can’t know) whether you’ve turned off cellular for those apps. They only see that your phone is using Wi-Fi or not using Wi-Fi.
So you can create a Shortcut automation:
- When you connect to Wi-Fi → Turn on “Wi-Fi Only” Focus, which allows or blocks certain apps.
- When you disconnect from Wi-Fi → Turn that Focus off, returning your notifications to normal.
It’s clever, but it’s also a giant kludge. Suppose you want to receive iMessage notifications while you’re out (because your phone number is your fail-safe for emergencies) but not get those from Slack or Facebook Messenger. The Focus mode lumps them all together: either you allow an entire app or you block it. Let’s say your boss has your phone number for urgent calls, but your Slack workspace is set to pester you about non-urgent stuff. iOS does not natively let you say, “Allow iMessage but block Slack, only if I’m on cellular, only during these hours.”
The problem stems from Apple’s push notification architecture. Apps get permission to send you notifications, often at any time, from Apple’s central push servers. They do not rely on your device’s own data toggles to decide whether to ping or not. So if an app has a message for you, Apple’s server sees an active device ID and tries to deliver it, no matter which type of connectivity you’ve turned on or off. From Apple’s perspective, that’s the entire point of push notifications. For them, it’s a feature, not a bug. If the developer or the user wants more nuance, well, Apple’s stance is “use Focus or the in-app notification settings.” It’s an incredibly paternalistic approach to software design—and it’s driving me to near madness.
Mindfulness, in principle, is about being present in the moment, letting go of anxieties about the past or future, and not falling prey to an endless swirl of reactive impulses. When you’re mindful, you choose how you spend your attention. You might look at the tree across the street and notice the interplay of sunlight on its leaves, rather than scrolling through endless TikTok videos to fill the empty space in your day.
But living mindfully in an iOS ecosystem can often feel like threading a needle blindfolded. You can almost do it, but there’s always some friction:
- Half-baked “Screen Time” restrictions that only apply to certain categories of apps (and can be easily overridden).
- Focus modes that, while helpful, can’t automatically adapt to more granular triggers like “cellular data for WhatsApp is currently disabled.”
- Push notifications that remain ungovernable at the system level: if an app has permission for notifications, iOS rarely cares whether it’s on cellular or Wi-Fi.

In a sense, Apple’s design philosophy is the epitome of “opinionated software.” They appear to believe that people should remain available for key alerts—like a boss summoning a subordinate at the press of a button. The problem is that not all alerts are key. The group chat about dinner tomorrow might not be critical until you actually want to see it. The random Slack mention for a “quick question” can absolutely wait until you’re at your desk. In the early days of smartphones, the novelty of immediate connectivity overshadowed the question of “Do we really need to see these notifications right now?” Now, a decade later, we’re grappling with the effect of being perpetually on the hook.
To be fair, Apple has tried to address some of these concerns. Do Not Disturb eventually evolved into Focus. We now have different modes for “Work,” “Sleep,” “Personal,” and more. We can also schedule them. But turning off notifications for an app across the board is a blunt instrument. Perhaps you want WhatsApp to notify you when you’re on Wi-Fi at home (where you can respond at your leisure) but not when you’re outside, paying 10 bucks for a cappuccino at a café, trying to enjoy the moment. iOS lumps these scenarios together unless you fiddle with Focus automations triggered by Wi-Fi connections. Then you realize that the minute you step outside your front door and lose Wi-Fi, your phone flips into a state where you do see the notifications that you were specifically trying to hide while away from home. The logic inverts precisely at the wrong time.
Apple’s ethos is famously minimalist (though changing). One hardware button for the iPhone’s home screen, no visible cooling fans on a Mac, a single piece of glass covering your watch face. That minimalism in design can be stunning—until you want to do something Apple decided was too “complicated” for the average user. They have a certain “if you need that level of control, perhaps you’re using it wrong” attitude. And it trickles down into features like push notifications, which are either on or off, with limited nuance (Focus modes aside).
This is reminiscent of the times I tried building websites from scratch. On the one hand, you have solutions like Squarespace or Webflow that promise “no coding needed,” but you soon discover that the moment you want a specific design quirk, you have to jump through hoops or pay extra. In response, you think, “Fine, I’ll do it from scratch,” only to realize you need a robust knowledge of HTML/CSS/JavaScript/Astro/Tailwind to do it elegantly. The result is a half-baked approach that ironically ends up more complicated because it’s too flexible.
iOS notifications are somewhat like the “Squarespace solution” to phone usage. Apple wants you in their curated environment. If you deviate, you’re forced to hack together solutions with automations and Focus modes. Meanwhile, if you’re the type of person who wants total control over your device, it starts feeling like an off-brand version of “I have neither the design nor the coding chops to make my vision come to reality.”
In letting loved ones know I’m restricting my chat and social media apps to Wi-Fi, I was aware it would inconvenience them. If we’re trying to coordinate a last-minute dinner while I’m on a train, the group chat might be blowing up with messages I won’t see until I connect to a hotspot. And yet, that’s exactly the trade-off I decided was worth it for my mental health.
The friction arises when iOS push notifications still tell me that these messages are arriving, even though I can’t read them. Apple’s system sees no difference between “no internet at all” and “internet limited by user choice.” The result is a hilarious half-solution: I still see the little red bubble or lock screen notification that something came in, but tapping it yields a “No connection” or “Try again later.” That’s psychologically more irritating than if I simply didn’t know a message arrived at all. It undercuts the entire boundary-setting approach, because now you’re forced to either (a) turn notifications for that app entirely off (b) endure pointless notifications or (c) use a Focus that lumps multiple apps together and flips states based on rudimentary triggers.
At times, it feels like Apple is living in a reality where “Why would you want partial connectivity?” is considered nonsensical. You’re either “connected” or you’re not—some kind of binary state. But life has nuance. People want to shape their connectivity around context, and iOS’s minimalistic approach to user-level scripting just doesn’t cut it. It’s ironically a maximalistic approach to your availability, pushing you to either accept all or reject all with limited nuance in between.
Sometimes, I find myself spiraling into a more philosophical vantage: Are we truly free, or are we simply tethered to illusions of choice? Technology can make us feel empowered—“Look, I can call anyone around the world!”—while also binding us to new forms of psychological captivity. In the second we sense some existential dread, we distract ourselves with push notifications. In that sense, iOS notifications aren’t just a nuisance; they’re micro-threads in a digital web that fosters dependence.
A friend once told me, “You only experience the world once, so why spend it responding to messages every time your phone buzzes?” The solution, for him, was an old-school Nokia phone with no data and no push notifications. But for me, that feels like an overcorrection. I do find joy in checking some group chats, sharing photos, and occasionally indulging in memes. The objective is balance, not abstinence.

Yet Apple’s design sometimes feels all or nothing. If you want to retain a partial connection—like Wi-Fi only for certain messaging apps—well, that’s on you to manually configure, to manually toggle Focus modes, to disclaim to your social circles that you might be slow to respond. Doing so for 1–2 apps is feasible. But once you expand that logic to your entire digital ecosystem—news apps, social media, random subscription apps that blow up your phone with deals or reminders—you’re stuck in a labyrinth of toggles and half-baked automations. The labyrinth is courtesy of Apple’s push notification architecture, which is designed to remain as frictionless as possible for app developers.
No wonder some people revert to simpler phones altogether: it’s the only surefire way to maintain sanity if you’re not willing to wrestle with Apple’s paternalistic structures.
At the heart of all this is Apple Push Notification Service (APNS). Every time an iOS device is online, it maintains a persistent connection to Apple’s servers—listening for notifications from any app that has permission. APNS doesn’t care if you’re on Wi-Fi, cellular, or standing on your head. If there’s a route to deliver a ping, it will do so, provided the device can reach Apple’s servers. When you toggle off cellular data for an app, iOS effectively says, “Ok, that app can’t fetch data,” but APNS is still allowed to pass along a notification payload if it’s using the system’s background connection.
In short, from Apple’s perspective, the push notification channel is separate from the app’s data usage. The app’s logic to fetch new messages might fail, but the push notification itself still arrives as a “hey, new content is here.” iOS doesn’t unify these states—so you end up with a meaningless ping.
If Apple were more flexible, we could see a scenario where you say, “If Cellular Data(WhatsApp) is OFF, then also disable push notifications for WhatsApp.” But that kind of conditional logic is not something iOS can do out of the box. It is “too complicated,” presumably, for the mainstream user. And so we’re left with Focus-based workarounds. That’s the friction point for mindful users: the tech “thinks” you want 24/7 availability, and pushing back requires a million micro-adjustments.
For now…I’m focusing on small wins:
- Manually disabling cellular data for chat apps like WhatsApp, Messenger, Signal and others.
- Turning off notifications entirely for the biggest attention hogs. If I can’t meaningfully customize them to reflect my partial connectivity, might as well keep them silent.
- Creating a custom Focus that lumps together “apps I might want to hear from if I’m on Wi-Fi”.
- Auto-enabling or -disabling the Focus if I’m on Wi-Fi.
- Communicating to friends and family that I’m not ignoring them, I’m just not seeing their messages in real-time.
These small changes hopefully cut down on the feeling of being perpetually “at the beck and call” of the digital sphere. In a way, it also fosters a return to older norms, where people had to plan meetups or calls in advance. We’re not beholden to the tyranny of “instant” communication if we all agree it’s not necessary 100% of the time.
I wrote this lambast not for the sake of complaining, but to share a real tension in the modern digital life: how do we set boundaries with technology when the ecosystem itself isn’t designed for those boundaries? If you’re reading this, you might be having a similar experience: tired of the constant buzz, the ephemeral floods of app alerts. Maybe you even tried using iOS’s built-in solutions only to discover that you were dancing around the edges of what Apple permitted, feeling more like a frustrated hacker than a mindful user.
Despite the friction, I see glimpses of progress. Apple’s incremental approach to user privacy has yielded advanced controls in other areas, like location or microphone access. Maybe one day they’ll unify data and push logic so that if you disable data for an app, push notifications will gracefully hold off. Or they’ll embed triggers in the Shortcuts app that say: “If user toggles off App X’s data, also toggle notifications off.” But as of iOS’s current state, that’s a pipe dream.
Still, we can choose to work with what we have, and sometimes that means explaining to your family, “Listen, I’m not on WhatsApp unless I’m on Wi-Fi. If you really need me, call me.” It’s not perfect, but it’s a step in reclaiming the headspace we inadvertently surrendered to these devices.
I want to keep reminding myself (and perhaps you, dear reader) that setting boundaries isn’t a rejection of technology—it’s a recognition that technology should serve our well-being, not the other way around. APNS may not respect these lines out of the box, but with some mindful choices and a bit of friction, we can nudge it in the right direction, one toggle at a time.
For now, that’s enough for me: a small step towards living a less tethered life, ironically in the same ecosystem I still enjoy for so many reasons. It might be inconvenient for a few folks, but sometimes inconvenience is the gateway to greater peace of mind. And I’d argue that’s worth a few missed messages while I stroll through the city, noticing the sunlight on the leaves again, phone (mostly) silent in my pocket.
