The menu bar is a publishing surface now — and someone finally treated it like one
I spend most of my working day inside scheduling dashboards, analytics tabs, and a browser with roughly forty open tabs across five client accounts. But the thing I actually glance at hundreds of times a day is my Mac’s menu bar. It’s where my timer lives, my VPN, my clipboard manager, my Focus mode toggle, and the little icon that tells me whether my upload queue is still churning. When that strip of pixels turns into a cluttered mess, my whole operating rhythm degrades — and I don’t think that’s a niche complaint. Anyone who runs social for a living is living in a menu bar, whether they’ve named it or not. That’s why Blenny, a small macOS utility that just launched on Product Hunt, is more interesting to me than its modest scope suggests. It’s not a social tool. But it’s a tool for the exact people who build and operate social tools, and the design decisions inside it are worth stealing.
Here’s the pitch in one line: Blenny gives your menu bar three states — Visible, Revealable, and Hidden — and lets you draft a layout, then apply it on your terms. The maker is a developer who goes by fish on Product Hunt, and the app is free, self-signed, and open source under Apache-2.0. That’s the whole product. No AI, no cloud, no subscription. And yet the operational philosophy behind it — draft first, apply deliberately, undo everything — is a better mental model for content operations than half the SaaS I’ve paid for this year.
What it actually solves, and why the “three states” framing matters
Most menu bar managers I’ve used fall into two camps. There’s the Bartender school, which is essentially a hide-and-reveal curtain: icons vanish, and you pull them back with a click or a hotkey. Then there’s the Ice school, which is more about taming the overflow with a cleaner second bar. Both are fine. Neither really gives you a draft state — a place to compose a layout before it goes live.
Blenny’s three-state model is the interesting part. Visible icons stay in the bar. Revealable icons are tucked but accessible. Hidden icons are out of the way entirely. Crucially, you can draft the groups and order, then Apply when you’re ready — and Undo restores the previous change. That’s not a cosmetic feature. That’s a workflow primitive. It means you can experiment with how your menu bar is organized the same way you’d experiment with a content calendar: stage the change, review it, ship it, and roll back if it breaks your muscle memory.
The maker is explicit about the mechanics: it never moves the pointer or simulates dragging, and it doesn’t need Screen Recording permission. That’s a meaningful trust signal for anyone who’s watched a utility ask for screen access and felt their stomach drop. Ordering does require Device Control permission and access to the menu bar layout file — which is a real ask, and worth understanding before you install. But the absence of Screen Recording is the kind of default I wish more tools shipped with.
Why the permission model is the real story
I’ve audited a lot of “productivity” apps for client machines, and the pattern is always the same: a tool that needs broad system access to do something you could describe in one sentence. Blenny’s maker draws a clear line — it manipulates the menu bar layout file rather than puppeteering your cursor. For a social media manager running a MacBook with client credentials on it, that distinction is the difference between “I’ll try this” and “absolutely not.” It’s also a reminder that the tools we recommend to our teams carry a security surface area, and “it’s free” doesn’t mean “it’s consequence-free.”
How it stacks up against the incumbents — and where the comparison gets uncomfortable
If you’ve been in the Mac utility world for a while, you know the names. Bartender has been the default for years, Ice emerged as a free open-source alternative, and Hidden Bar is the minimalist’s choice. So where does Blenny fit?
My take: Blenny isn’t trying to be a full Bartender replacement. It’s narrower and more opinionated. The draft-apply-undo loop is genuinely different from the “configure once and forget” model most of these tools use. And the fact that it manages apps with several menu bar icons together is a small but real quality-of-life win — anyone who’s tried to wrangle a multi-icon app like a VPN client or a sync tool knows the pain of icons that refuse to stay grouped.
But here’s where the comparison gets uncomfortable, and I want to be transparent about it. The maker lists caveats up front, and they matter:
- The app is self-signed, not Apple-notarized. On modern macOS that means a Gatekeeper warning and a manual approval dance. For a solo operator, fine. For a team deploying to a fleet of machines, that’s friction.
- Some unattributed icons can disappear while management is active. That’s a real bug class, not a nitpick.
- Clicking the clock won’t open Notification Center until you stop management — though the trackpad gesture still works.
- Multi-display setups haven’t been tested.
That last one is the dealbreaker for a lot of creators I know. If you’re running a MacBook plus an external monitor — which is basically the default setup for anyone editing video or managing multiple accounts — you’re in untested territory. The maker is honest about it, which I respect, but “untested” is not “works.”
Where the math breaks
Let me do the operator’s math on this. Blenny is free, open source, and built specifically for macOS 27 on Apple silicon. That’s a very narrow target. If you’re on an Intel Mac, or you haven’t upgraded to the latest OS, or you’re on a managed corporate machine that blocks self-signed apps, you’re not the audience. And if you’re the kind of person who wants a polished, notarized, support-contract experience, Bartender or Ice will serve you better today.
But if you’re a solo creator or a small-team operator who’s comfortable with a README, a GitHub issue tracker, and a bit of manual setup, the trade is reasonable. You’re trading polish for a workflow model that’s actually different. And you’re trading a subscription for zero dollars. I’d bet the maker knows exactly how narrow the audience is — the caveats read like someone who’s been burned by overpromising before.
What social media operators should steal from this
Here’s the part I actually want you to take away, because it has nothing to do with menu bars. The draft-apply-undo loop is the single best mental model I’ve seen for content operations this year, and it’s hiding inside a tiny macOS utility.
Think about how most teams ship content. Someone drafts a post in a doc, someone else schedules it in Buffer or Later, and it goes live. There’s no staged preview state. There’s no clean rollback. If the post flops, you learn from it after the fact. If it goes out with a typo, you’re editing live.
Now imagine applying Blenny’s model to your calendar. You draft the week’s posts in a staging view. You review the whole layout — the order, the grouping, the mix of formats — before anything goes live. You hit Apply. And if the week underperforms, you have a clean Undo that restores the previous state, so you can compare against a known baseline instead of guessing.
That’s not a feature request. That’s a discipline. And it’s the discipline most social teams are missing. We talk endlessly about content repurposing workflows and UTM tracking and API rate limits, but we rarely talk about staging. The best schedulers have a draft state, but almost none have a true “apply and undo” model for the whole calendar.
Why TikTok creators should care more than LinkedIn ones
If you’re publishing to TikTok, your content cadence is brutal. You’re posting multiple times a day, testing hooks, riding trends, and killing underperformers fast. A staged calendar with a clean rollback is worth more to you than to someone posting once a week on LinkedIn. The faster your iteration loop, the more valuable a draft-apply-undo model becomes. LinkedIn rewards consistency and depth; TikTok rewards volume and speed. Blenny’s philosophy maps to the latter.
The permission lesson for tool evaluators
The other thing worth stealing is the permission discipline. When you’re evaluating a new scheduling tool or analytics platform for your team, ask what it actually needs access to. Does your social scheduler need your Google Analytics read scope? Does your AI caption tool need your camera roll? The answer is usually “no, but it’s easier.” Blenny’s maker chose the harder path — no Screen Recording, explicit Device Control — and documented the tradeoff. That’s the standard I’d hold your next SaaS purchase to.
Where I think it falls short — and who should skip it
I want to be balanced here, because the temptation with a small open-source launch is to either dunk on it or overpraise it. Let me be clear about both.
The limitations are real and documented. Self-signed means Gatekeeper friction. Untested multi-display means a large chunk of the creator audience is on their own. The clock/Notification Center quirk is annoying. Unattributed icons disappearing is a bug you’ll want to report on GitHub rather than tolerate. And macOS 27 on Apple silicon is a hard floor — not disclosed is any roadmap for Intel or older OS support.
My take: this is a tool for tinkerers, not for teams. If you’re a solo creator who enjoys a README and doesn’t mind filing a bug report, it’s a genuinely interesting experiment in menu bar UX. If you’re a social media manager deploying tools across a team of five, this isn’t ready for that — and the maker isn’t pretending it is. That honesty is worth more than a polished landing page.
The bigger open question is whether the draft-apply-undo model is a feature or a philosophy. If it’s a feature, it’s a nice menu bar utility. If it’s a philosophy, someone should build it into a content calendar. I’d bet on the latter being the more valuable insight.
What I’d watch / test next
If you want to act on this week, here’s what I’d do. First, if you’re on Apple silicon and macOS 27, install Blenny from the Product Hunt launch page, read the README, and test the draft-apply-undo loop on a single display. Pay attention to whether the staging model actually changes how you think about your menu bar — because if it does, you’ll start wanting it everywhere else.
Second, audit your content calendar for a staging gap. Pick one platform — I’d start with TikTok or Instagram — and build a manual draft-review-apply step into next week’s schedule. Use a doc or a spreadsheet as your staging layer. See if the rollback discipline changes your iteration speed.
Third, when you evaluate your next scheduling tool — Metricool, Hootsuite, Sprout Social, whoever — ask the permission question and the staging question. If the tool can’t answer both, you’ve learned something.
And fourth, if you try Blenny and hit a bug, file it on GitHub. The maker asked for specific reports, and that’s how small tools get better. The menu bar is a publishing surface. Treat it like one.
