The Arc Paradox: Why I Churned

My MacBook M1 Air was burning my lap.

The battery, usually a 10-hour fortress, was dead in four hours. The culprit wasn’t due to heavy CPU tasks or a program going crazy in the background. It was the application I had evangelized to every friend I have: The Arc Browser.

I didn’t just use Arc; I relied on it. As someone with multiple businesses, I live in “account hell.” Google logins clash with Zoho Books, and switching brands meant a clumsy dance of signing out and signing in.

Arc’s “Spaces” fixed this. It gave me completely isolated sessions in one window. It felt like magic. I sold it to everyone.

The Decay of Novelty

Then came the pivot.

The Browser Company announced Dia, an AI-first tool, effectively sunsetting their Arc Browser, which many had come to love. CEO Josh Miller admitted Arc was “too different for too little reward.”

Suddenly, the product I championed started rotting. The battery drain wasn’t a bug; it was neglect.

I didn’t wait. I switched back to Safari, which had quietly copied Arc’s “Profiles” feature. Later, I moved to Zen Browser, an open-source alternative that gave me the same vertical tabs without the thermal throttling.

The Hard Lesson for Builders

Here is the brutal truth I have to admit as a user: I loved Arc, but I would never have paid for it.

The problem it solved (account switching) was annoying, but not expensive. It was a “vitamin,” not a “painkiller.” And as Safari and Zen proved, the features I loved were easily commoditized.

What I learned from documenting this: Elegance attracts early adopters. Stability keeps them. But only “pain” makes them pay. Arc had elegance, but when stability broke, the elegance didn’t matter. And the pain wasn’t high enough to justify a subscription.

Your takeaway: If your “moat” is a UI feature (like vertical tabs), you don’t have a moat. You have a head start.

Key takeaway: Survivability > Elegance. I’ll take a boring browser that saves my battery over a magical one that kills it.