Supper Club × Arc Browser with Hursh Agrawal

Episode Summary

Executive Summary: Hirsch Agarwal, co-founder and CTO of The Browser Company, explains why Arc was built: browsers are the most-used software many people have, yet UX innovation has stagnated. He details Arc’s product philosophy, native Swift-based architecture atop Chromium, feedback-driven iteration, monetization plans, and future directions like Windows, mobile, and developer-focused features.

Main Topics: Why build Arc at all: Hirsch frames browsers as the most-used but least-innovated category of software, motivating Arc as a product-led rethink of core browser UX. Product philosophy and UX innovation: Arc adds tabs-on-the-side, auto-archiving, pinned/explore tabs, previews, themes, and command-palette-driven workflows to solve tab overload and improve discoverability. Technical architecture and performance: The team initially prototyped in Electron/React, then moved to a native Swift/AppKit/SwiftUI shell over Chromium to overcome performance and compilation bottlenecks. Feedback-driven development: Arc is built through rapid iteration, dogfooding, and direct user feedback, with product decisions heavily influenced by complaints, bug reports, and internal usage. Business model and incentives: The company wants a subscription or team-based model rather than ad/search-referral dependence, to preserve product incentives and avoid conflicts seen in browser incumbents. Platform expansion and roadmap: The discussion covers Windows support in progress, uncertainty around iOS due to WebKit limits, and future browser/developer tools including a developer mode and Boosts. Design craft and personalization: Arc’s aesthetics, sound, theming, and interaction details are treated as central, with design done heavily in code and tuned for a daily-use workspace.

Key Arguments: Browsers have remained visually and functionally stagnant for years despite the web itself evolving rapidly. Browser complexity is not just technical; product decisions like tab management are necessary to solve user behavior, not just RAM usage. Arc’s sidebars, pinned tabs, and auto-archiving address tab overload by treating unused tabs as a product problem rather than a user failure. Native UI in Swift was necessary because a JavaScript/Electron-based browser felt too slow and stuttery for a daily browser experience. Chromium is treated as infrastructure; Arc’s differentiated value comes from the app layer and interaction model on top. The team iterates quickly and relies on dogfooding because browser habits are deeply ingrained and many ideas that seem good in theory fail in daily use. The browser company wants a revenue model aligned with users, likely subscription-based, so the product is not beholden to search ads or referral economics. Developer-focused features are a major opportunity, especially better browser tooling, local-host modes, and fast website customization via Boosts.

Data Points: Company age at time of discussion: about 3 years - Hirsch says the browser company started about three years earlier First company founding year: 2011 - He and his co-founder dropped out of school to start Branch in 2011 Branch acquisition timeline: after about 3 years - Branch ran for roughly three years before being acquired by Facebook Typical browser usage: 40-50 hours per week - Used to explain why browser UX details matter so much Chromium clean build time: about 4.5 hours - Used to illustrate how slow Chromium builds can be without caching Chromium incremental build time: 3-4 minutes - Used to describe iteration friction during browser development Arc prototype timeline: 8 months - First Electron-based prototype launched about eight months after starting Auto-archive threshold examples: 24 hours, 7 days, 30 days - Configurable archival windows for old tabs Auth0 Developer Day locations: London on September 29; Berlin on October 5 - Sponsor announcement during episode Auth0 event length: 1 day - Developer Day described as a one-day event Auth0 workshop length: 2 hours - Hands-on workshop included in the event Feedback response rate: 100% of incoming feedback read and responded to - Hirsch says every feedback report is read by the membership team Firefox revenue share from Google: 98-99% - Mentioned as Mozilla’s main revenue source from search referrals Windows support ETA: sometime next year - Arc is being worked on for Windows with a rough target of next year

Pivotal Quotes: "the one product we spend the most time in during the day ... is the one single one that hasn't really changed from a UX point of view" — Hirsch Agarwal: Explaining the motivation for building Arc "The browser really hasn't been taking a lot of the responsibility for helping you manage your life and your overload." — Hirsch Agarwal: Describing Arc’s tab management and archiving philosophy "Chromium, to us, is largely infrastructure." — Hirsch Agarwal: Explaining Arc’s architecture and how the browser company thinks about the engine

Implications: Arc suggests the next browser battleground is UX, workflow, and product design—not engine wars. If successful, subscription-funded browsers could create more user-aligned innovation, especially for power users and developers.