The Launchpad lesson every cross-border operator should steal
Cross-border sellers spend their days inside terrible interfaces. Amazon Seller Central buries a fee change three menus deep; Shopify’s admin swaps a setting’s location every other release; TikTok Shop seller center ships a new module before the old one is deprecated. So when a solo developer rebuilds a beloved macOS utility because Apple deleted it, that story is not really about Mac apps. It is about what happens when a platform owner decides your muscle memory is expendable — and what an operator can do about it. Launchie, built by Nick Friedrich, is the case study worth reading closely.
What Launchie actually solves, and why the shape of the problem matters
The origin story is simple and specific: when macOS 26 Tahoe removed Launchpad, Friedrich lost the way he had opened apps for years — “a grid I had arranged myself, with folders I could find without reading a single name.” Apple’s replacement, the Apps view inside Spotlight, sorts everything automatically and refuses to let users create folders. macOS 27 kept it that way. So he built the Launchpad he missed, then extended it.
The feature list he shipped is deliberately unglamorous. Your own layout, with drag-anywhere positioning and unlimited folders, free. Spaces — separate pages of apps for work, games, or design, switched with a swipe. Instant search plus Quick Access for recent and most-used apps. A Pro tier adds the wallpaper blurred behind the grid like the original, hot corners, hidden apps, and a pinch gesture that opens Launchie instead of Apple’s Apps view. It is a one-time purchase with no subscription, distributed through the Mac App Store, as a direct download, and via Homebrew (brew install --cask launchie).
Notice what is absent. No AI copilot. No cloud sync. No team workspace. No “reimagined productivity OS.” Just a restoration of a workflow that one platform owner unilaterally deleted, plus a handful of power-user affordances the original never had.
That restraint is the interesting part, and it is the part cross-border operators keep getting wrong.
Why Amazon sellers should care more than Shopify ones
Shopify merchants live in an ecosystem where the platform’s own admin is only one of a dozen surfaces they touch. Most serious DTC brands have already abstracted away from the native admin — they run fulfillment through a 3PL dashboard, customer support through a helpdesk, marketing through Klaviyo, analytics through a warehouse. Losing a button in Shopify’s admin is annoying but rarely existential.
Amazon sellers are the opposite. Their entire operating surface is Amazon Seller Central, a system they do not control, cannot fork, and cannot replace. When Amazon changes the fee structure, reshuffles the advertising console, or renames a report, there is no third-party equivalent to fall back on. The Launchie story — platform owner removes a feature, power users lose years of accumulated workflow — is the default state of being an Amazon seller. The only difference is that Apple’s change was a one-time event, and Amazon’s changes arrive quarterly.
The practical hedge is the same one Friedrich executed: own the layer that sits between you and the platform. For Amazon operators that means keeping your own product data, your own ad-spend history, and your own keyword tracking outside Seller Central. Tools like Helium 10 or Jungle Scout are useful precisely because they hold a copy of data the platform would rather you query live. The moment your entire institutional memory lives inside a UI someone else controls, you are one release note away from Friedrich’s problem.
How Launchie differs from the options already on the shelf
The launcher category is not empty. Raycast has become the default power-user answer on macOS, with an extension ecosystem that turns it into a command bar for almost anything. Alfred has held that position for over a decade. Spotlight itself is the incumbent by default, and Apple’s Apps view is the specific thing Launchie is reacting against.
Launchie’s differentiation is not feature depth — it will lose that fight against Raycast’s extension store, and it should not try to win it. The differentiation is spatial memory. Raycast and Alfred are keyboard-first: you type, you get a result, the interface is a list. Launchie is grid-first: you arrange, you remember positions, you click. Those are different cognitive models, and the people who relied on Launchpad for a decade are not well served by a command palette, no matter how fast it is.
The pricing model is the second differentiator, and it is the one I would flag for anyone building in this space. Raycast runs a freemium model with a Pro subscription; Alfred gates its Powerpack behind a paid license. Launchie is explicitly a one-time purchase with no subscription. For a utility this narrow, that is the correct call — the ceiling on what a launcher can charge monthly is low, and subscription fatigue among Mac power users is real. Friedrich is also shipping where his users already are: Homebrew distribution matters for the developer-adjacent crowd, and the Mac App Store listing handles the people who will never open a terminal.
The distribution lesson for tool builders
If you run a SaaS product for cross-border sellers — a repricing tool, a review automation layer, a returns portal — watch how Launchie is distributed. Three channels, three very different audiences, one codebase. The Mac App Store is discovery and trust. The direct download is margin and control. Homebrew is credibility with the technical segment that influences everyone else.
Most e-commerce SaaS founders pick one channel and stop. The Shopify App Store is treated as the whole strategy, or the Amazon Selling Partner API marketplace, or a cold-outbound motion. The operators who win treat distribution as a portfolio. A Shopify App Store listing that catches long-tail search, a direct integration for the brands who will never install from a marketplace, and a presence in the communities where your buyers actually argue about tools — those are three different jobs and they need three different assets.
What cross-border sellers can borrow from a Mac launcher
Strip away the platform specifics and Launchie is a case study in three operator habits that translate directly to e-commerce.
First: treat your personal workflow as infrastructure, not preference. Friedrich did not accept Apple’s replacement. He rebuilt the thing that worked for him. The equivalent for a seller is refusing to run your business inside whatever default view Seller Central or Shopify hands you. Build the spreadsheet, the Notion database, the internal dashboard — the layer that reflects how you actually think about your catalog. The platform’s UI is optimized for the platform’s metrics, not yours.
Second: ship the boring features first. Unlimited folders. Drag-and-drop. Search. These are not exciting. They are also the entire reason anyone used Launchpad. In e-commerce terms, this is the argument for fixing your returns flow before you build a loyalty program, or getting your inventory sync correct before you add a subscription option. The unglamorous layer is where retention lives.
Third: let user requests drive the roadmap. Friedrich says that since the 2025 launch, most new features have come from user requests, and he closes his launch post by asking what people used Launchpad for and what is still missing. That is not a marketing gesture — for a solo developer competing against Apple, it is the only sustainable product strategy. The platform owner has distribution and defaults. The challenger has responsiveness.
Where the math breaks
I want to be honest about the ceiling here, because the temptation to over-extrapolate is strong.
Launchie is a solo-developer utility with a one-time purchase price and a narrow audience of macOS users who specifically missed Launchpad. That is a real business, but it is a small one, and the moat is thin. Apple can restore folder support to the Apps view in any point release and evaporate a chunk of the demand overnight. Raycast can ship a grid view. Neither is likely, but neither is impossible, and Friedrich has no structural defense against either.
The same fragility applies to every tool built on top of a platform you do not own. A repricing tool that depends entirely on Amazon’s SP-API can be killed by a policy change. A TikTok Shop analytics dashboard lives or dies with TikTok Shop’s data access. The Launchie story is a reminder that “the platform removed the feature” is not a tail risk — it is the base case.
Where my judgment says Launchie falls short
Three things bother me about this launch, and they are worth naming because they are the same three things that bother me about most indie tools in the e-commerce stack.
The Pro tier is underspecified. Blurred wallpaper, hot corners, hidden apps, and a pinch gesture. That is a thin list to justify an upgrade, and it is the kind of feature set that reads as “we needed a paid tier” rather than “this is worth money.” Compare it to what Raycast Pro bundles — AI, cloud sync, custom themes — and the value gap is obvious. For a seller evaluating a paid tool, this is the same test: does the paid tier unlock a capability, or does it just remove an annoyance?
No sync story. Spaces for work, games, and design are great until you have two Macs and have to arrange everything twice. Friedrich does not mention iCloud sync or any cross-device mechanism in the launch copy, which for a layout-centric tool is a genuine gap. Any operator running a multi-device team will feel this immediately.
The free tier may be too generous. Unlimited folders and full layout control, free. That is the right call for adoption, but it leaves the paid tier competing against a free version that already solves the core problem. It is the same trap subscription-box brands fall into when their entry SKU is so complete that nobody upgrades.
The comparison that matters for operators
Put Launchie next to the tools cross-border sellers actually pay for — Shopify itself, TikTok Shop, Temu, SHEIN, Etsy, eBay — and the difference in stakes is enormous. Those platforms are where revenue happens. Launchie is where a developer’s afternoon happens. The reason I am writing about it anyway is that the structural dynamic is identical: a platform owner makes a decision, a user base absorbs it, and the only question is whether anyone builds an alternative in time.
Most cross-border sellers will never install Launchie. But every one of them is living through some version of the same story, and the ones who recognize the pattern early are the ones who keep their margins when the next platform decision lands.
What I’d watch / test next
This week, do three things.
Open your Seller Central or Shopify admin and list every workflow you would lose if the platform removed one feature tomorrow. If the answer is “most of them,” you have a data-ownership problem, not a tooling problem. Export what you can, today.
Then look at your own product’s distribution the way Friedrich structured his: one channel for discovery, one for margin, one for credibility. If you are only in the Shopify App Store, or only selling on Amazon, you are one policy change from Friedrich’s Tahoe moment.
Finally, go read the Launchie launch thread and watch how a solo developer handles feature requests in public. That responsiveness is a competitive weapon, and it is one of the few advantages a small operator has against a platform that will never return your email. The launcher itself is a niche Mac utility. The operating posture behind it is not niche at all.
