What Bark is, in one sentence
Bark is a small iOS app that turns a simple web request into a push notification on my iPhone. Nothing else: no feed, no chat, no account to manage, no ads.
I first came across Bark because I wanted reminders about my website, so I could know its status.
It is a system-level push, not an in-app message
Bark pushes travel through Apple's own push service, APNs. That is the same channel the iPhone itself uses for system notifications. The message does not wait inside an app for me to open it; iOS puts it straight on the lock screen.
That is also why killing the app changes nothing. I can swipe Bark out of the background completely, and the next push still arrives. The push does not depend on Bark running, because Bark is not the one delivering it — iOS is. The only things that can stop it are the obvious ones: notifications turned off for Bark, the phone offline, or the app deleted.
Immediacy: it arrives without me checking anything
A website does not remind me unless I open it. A chat message waits inside a chat app, under a pile of other chats. An AI assistant waits for me to ask it something. A Bark push is the other way round: when something happens, the phone lights up and tells me, whether or not I was thinking about it. For a reminder, that direction matters more than anything else.
Battery: it costs almost nothing
A reminder app that polls — checking a server every few minutes to ask "anything new?" — keeps waking the phone up. A chat app that holds a connection open and refreshes in the background does the same. APNs works the other way: one system connection, shared by every app on the phone, stays quiet until a message actually comes. Nothing polls, nothing runs in the background, and the phone does not spend battery waiting.
That is why I care about it in the field. Outdoors, or on an emergency job, battery is the scarcest thing I have. A reminder that drains the phone to tell me something is worse than no reminder at all. A push that arrives through the system channel, with no app running, is the cheapest way I know to get a message onto the phone.
Clean messages, and a high permission level
A Bark message is only a title and a body. There is no group chat around it, no social feed under it, no advertisement attached to it, and no need to open anything to read it. When it arrives, it is the whole message.
Its permission level is also higher than an ordinary in-app note. It is a real iOS notification, so I can allow it through Focus as a time-sensitive notification, and it still shows on the lock screen when the phone is locked and silenced. A message inside a chat tool or a website cannot do that on its own — it first has to become a push, and then it is competing with every other chat notification for attention.
Hands-free: Siri reads it aloud, so I do not have to look at the screen
There is one more reason I keep Bark on, and it has nothing to do with Bark itself. It is an iPhone feature called Announce Notifications (in Chinese iOS: 播报通知).
When it is on, Siri reads a new notification aloud: first the name of the app it came from, then the message itself. A Bark push therefore sounds like: "Bark" — and then the title and the body, spoken out. I do not have to pick up the phone, unlock it, or look at the screen at all to know what happened, the first time it happens.
To turn it on: Settings, then Accessibility, then Siri, then turn on Announce Notifications on Speaker, and for each app choose whether to announce all notifications or only time-sensitive ones. That is the version I use: no headphones, no CarPlay, nothing connected at all — the phone reads the message straight out of its own speaker. (Announce Notifications also works through compatible AirPods or Beats headphones and through CarPlay, but I do not need either of those.)
One practical limit I have noticed, and Apple support could not give me a specific number for: what Siri reads aloud from the speaker is short. In practice only about ten to twenty characters get spoken. The full message still shows on the screen, but what I hear without looking is just the beginning of it. So for a Bark reminder, the important words have to come first — the rest is there to read later, not to hear.
In the field, that is the part I value most. Hands may be busy, gloves may be on, eyes may be on the road or on an antenna — and still the message reaches me, spoken, the moment it arrives. A reminder that requires me to stop what I am doing and look at a screen is a reminder I will miss exactly when it matters.
So why Bark, when chat tools and AI assistants already exist?
Because they solve a different problem. A chat tool is for talking to people; its messages get buried, muted, and mixed with everything else. An AI assistant is for asking questions; it answers when asked, it does not tap me on the shoulder when something happens. A website is for looking things up; it does not come to find me.
Bark does one job and nothing else: when something happens somewhere else, put a short, clean message on my lock screen, right now, without running anything in the background and without spending battery waiting. That is why I use it for reminders, and why the next article builds a relay around it instead of sending reminders through a chat group.
For ham radio contacts, I find Bark a very suitable little reminder tool.
In this series: One App, Two Websites: Instant Ham Radio Reminders — register on GitHub and Cloudflare by hand, and deploy the Bark relay Worker, step by step. Satellite Pass Reminders by Hand: Start at 30 Degrees — use that relay for satellite pass reminders, starting at 30 degrees. Bark + SDR: Never Miss a Satellite Recording Again — a script watches the recording folder and pushes when a satellite recording finishes. Bark + SDR: Get Pushed Only When the Repeater Talks — a push only when squelch opens on one repeater frequency. Bark + SDR: A Push When the Band Opens to You — a push when WSJT-X decodes what you want. Bark + SDR: Know When Recording Finishes or Fails — a push when a long recording finishes, when disk space runs low, or when the expected file never appears.
我为什么用 Bark 来做提醒
Bark 是什么，一句话讲清
Bark 是一个很小的 iOS 应用，它把一次普通的网络请求变成我 iPhone 上 的一条推送通知。别的什么都没有：没有动态，没有聊天，没有要管理的 账号，没有广告。
我第一次接触 Bark，是为了网站的提醒，好知道网站的状态。
它是系统级推送，不是应用内消息
Bark 的推送走的是苹果自己的推送服务 APNs，也就是 iPhone 系统本身 用的那条通道。消息不是先在某个应用里等着我去打开，而是由 iOS 直接放到锁屏上。
所以把 Bark 从后台杀掉也没有关系。我可以把 Bark 的后台彻底划掉， 下一条推送照样到。因为递送这条消息的不是 Bark 本身，而是 iOS 系统。 真正能拦住它的只有几件明摆着的事：Bark 的通知权限被关了、手机断网了、 或者应用被删了。
即时性：不用我去查，它自己来找我
网站不会提醒我，除非我打开它。聊天消息躺在聊天应用里，压在一堆 别的聊天下面。AI 助手要等我去问它，它才回答。Bark 的推送是反过来的： 事情一发生，手机就亮起来告诉我，不管我当时有没有想起这件事。对提醒 来说，这个方向比什么都重要。
省电：几乎不花电
那种轮询的提醒应用，每隔几分钟就去问一次服务器“有新东西吗”， 会一次次把手机吵醒。聊天应用在后台保持连接、不断刷新，也是这样。 APNs 是反过来的：全手机共用一条系统连接，平时安安静静，只有消息 真正来了才动一下。不轮询，不在后台跑，手机不用花电去等。
这就是为什么我在野外在乎它。到了野外，或者出了应急任务，电池是 我最缺的东西。一个为了提醒我而先把电耗掉的提醒，还不如没有提醒。 走系统通道的推送，不用跑任何应用，是我知道的最省电的办法。
消息干净，权限级别也高
一条 Bark 消息只有标题和正文。它外面没有群聊，没有动态，没有广告， 不用打开任何东西就能读完。
它的权限级别也比普通的应用内消息高。它是真正的 iOS 通知，我可以 把它设成限时通知，让它穿过专注模式，而且手机锁屏、静音的时候它 照样显示在锁屏上。聊天工具或者网站里的消息自己做不到这一点——它 们先得变成推送，然后还得跟所有别的聊天通知抢注意力。
不用看屏幕：Siri 读出来，第一时间就知道
我一直开着 Bark，还有一个原因，而这个原因跟 Bark 本身没有关系。 它是 iPhone 自带的一个功能，叫播报通知（英文叫 Announce Notifications）。
开着它的时候，Siri 会把新通知读出来：先说这是哪个应用来的，再读 消息本身。一条 Bark 推送听起来就是这样：先说“Bark”，再读出标题 和正文。我不用拿起手机、不用解锁、不用看屏幕，第一时间就知道 发生了什么。
开法是：设置，点无障碍，点 Siri，把“在扬声器上播报通知”打开， 再按每个应用选是播报全部通知还是只播报限时通知。这就是我用的版本： 不用耳机，不用 CarPlay，什么都不用连，手机直接用自己的扬声器把 消息读出来。（播报通知也能走能用的 AirPods、Beats 耳机和 CarPlay， 但我不需要那些。）
还有一个我实际注意到的限制，问过苹果客服也没有给过具体数字： 扬声器读出来的内容很短。实际听下来，能读出来的大概就是十来个字、 最多二十个字左右。完整消息还是会显示在屏幕上，但不看屏幕能听到的 只有开头那一点。所以 Bark 提醒最重要的话必须放在最前面，后面的 是留着以后看的，不是靠听的。
在野外，这一点是我最看重的。手可能正忙着，手套可能还戴着，眼睛 可能正看着路或者看着天线，消息还是在来的那一刻就用语音到了。 一个非要我停下来看屏幕的提醒，恰恰会在最要紧的时候被错过。
所以，有了聊天工具和 AI 助手，为什么还要 Bark？
因为它们解决的是不同的问题。聊天工具是用来跟人说话的，消息会被 淹没、被静音、跟别的东西混在一起。AI 助手是用来问问题的，它等我 问，它不会在事情发生的时候拍我肩膀。网站是用来查东西的，它不会 主动来找我。
Bark 只干一件事，别的一概不干：别处一有事情，就立刻把一条简短、 干净的消息放到我的锁屏上，不用在后台跑任何东西，也不用花电去等。 这就是我用它来做提醒的原因，也是下一篇不走聊天群、而是搭一个 转发器的原因。
我觉得 Bark 是一个非常适合用在业余无线电通联提醒上的小工具。
这个系列里还有：一个 App，两个网站：业余无线电即时提醒——手动注册 GitHub 和 Cloudflare，一步一步部署 Bark 转发 Worker。卫星过顶提醒，亲手做：先从 30 度起——用那个转发器做卫星过顶提醒，先从 30 度起。第 4 篇：卫星录音——录音文件夹里文件一完就推送。第 5 篇：中继守听——静噪打开才推送。第 6 篇：波段打开——WSJT-X 解出你要的台才推送。第 7 篇：录音状态——录音完成、磁盘不足、预计文件没出现都推送。