gurupanguji
The eerie quiet of 6:00 AM coffee is a strange time to realize a favorite tool might be "in trouble." I was scrolling through a Reddit thread drafting an obituary for Alfred, the Mac app launcher I have used so long my fingers move before my brain does. To the commenters, Alfred is stagnant because it isn't releasing visual updates or just plain releasing updates at the same cadence as Raycast. I worry when we believe that if a piece of software isn't constantly shifting its visual UX, it is dying.
There is a deep dissonance here between what we perceive as "active" software and what actually constitutes a stable business. It is the difference between a cast-iron skillet and a smart appliance. One has a clear premise: it sears meat and lasts for generations because its "technology" is local and requires no external permission to function. The other is a promise of future convenience that only works as long as the manufacturer's servers stay on and the venture funding keeps the lights on at the office.
The Perceived Decay
A sharp wince is an uncomfortable way to start a morning. It isn't the coffee, which feels just right. It is the realization that a digital tool I have used for a decade is being drafted for an obituary. On Reddit, the consensus is clear: Alfred is "in trouble" because it hasn't pivoted. It hasn't announced a venture-backed "AI engagement point" or a flashy new UI. It seems like the community conflated iterative feature-creep with foundational stability.
This is not a tirade against LLMs. In the eerie quiet of my office, I just used an LLM to fix a broken footer on my website in minutes. The pace of deployment is intoxicating, but it masks a fragile truth. We now judge a tool's pulse by the frequency of its visual updates rather than the structural longevity of its business. We have started thinking superficially about what makes software last, assuming that if a developer isn't shouting into the void, they must be drowning in it. We have to wonder if "lasting" is even a goal we still value.
The Economics of Longevity
The ceramic mug in my hand is a local solution to a physics problem. It doesn't require a firmware update to hold coffee to remain a vessel. It is functional, silent, and stable. This is the structural premise of Alfred. It is a self-funded, local-first tool with almost no dependency on a cloud instance. Its primary costs are human: a few developers ensuring it stays patched for the latest macOS update. Its economic incentives are aligned with its longevity because its survival isn't tied to a growth-at-all-costs mandate. It costs very little to run freely and it charges for the powerpack, which seems like it could be profitable.
The architectural dissonance lies in the mismatch between a tool’s functional premise and its underlying economic incentives. Raycast, by contrast, is a venture-subsidized experiment. There's no value judgement here about venture-subsidized experiemnts. Innovation requires money and I am glad we get to try different things. Raycast's shift from a launcher to an "AI engagement point" isn't just a feature update; it is a fundamental change in its supply chain. By pivoting to the cloud-heavy requirements of LLMs and expanding to Windows, my thesis is that they are building a "smart appliance" that requires constant external power. This power comes from both compute and venture capital and a new, modern way to engage its community. If the cashflow or the cloud infrastructure or the community engagement disappears, the tool follows. We are witnessing a divergence between local-first solvency and the precarious beauty of a venture-backed pivot.
I must admit that the community engagement is a marketing mechanic that has both pros and cons. The pros are a very engaged community and a hundred voices amplifying your latest feature and converting other users. On the other hand, rampant viral growth has the downsides. You don't need it when unit economics are strong and there is a real cost to maintaining a community.
The Aspiration of Sovereignty
The quiet of this morning represents the freedom I am working toward. After years on the corporate treadmill, I find myself aspiring to build a lifestyle business: a "hearth" rather than a "high-rise." It is a choice to optimize for sovereignty over scale, seeking a niche of users who look beneath the superficial churn of visual updates to understand the structural integrity of their tools. I want to build things that don't require me to be beholden to venture capital or the noise of a constant pivot.
Yet, as I sit here with my coffee, I have to wonder: is this a truly rational path, or am I merely rationalizing a desire for peace? There is a seductive comfort in the idea of a self-contained, local-first business. In a world of hedonistic adaptation, where users are trained to expect a hit of dopamine with every new feature, stasis can feel like a death sentence. Am I projecting my own need for stability onto a market that only values momentum? This is the fundamental gamble of the lifestyle business. It requires setting an honest expectation with the user: you are paying for a tool that works, not a promise that it will constantly change.
Right after I hit publish, Raycast rolled this out
They are becoming a software house - the new product looks very interesting. I am glad they were able to work on this. However, similar to the Arc browser saga and Dia, one can't comment that Alfred will die while Raycast will survive.