Josh Miller on Arc and The Browser Company

Josh Miller on Arc and The Browser Company

transcript product-craft browser company-building product-philosophy lenny-podcast

Josh Miller on Arc and The Browser Company

Guest: Josh Miller — CEO and co-founder of The Browser Company; makers of Arc.
Host: Lenny Rachitsky
Source: Lenny’s Podcast.

Overview

Josh Miller is the CEO of The Browser Company, which builds Arc — a browser that became Lenny’s default browser. The conversation covers The Browser Company’s product philosophy (optimise for feelings, not metrics), culture (heartfelt intensity, prototype-driven), hiring, building in public, and the long-term vision of Arc as an “internet computer” that replaces the traditional browser as the interface to a cloud-native computing world.

Key ideas

  1. Optimise for feelings, not metrics. Silicon Valley has over-indexed on graphs and numbers. The Browser Company asks instead: how do we want the user to feel? Joy, speed, focus, surprise. When you get that right, the metrics follow — viral sharing happens naturally when people feel surprised and delighted.
  2. Heartfelt intensity as the primary hiring criterion. Everyone on the team shows up with fire: something specific they are out to prove. This drives the culture more than any process.
  3. Assume you don’t know. A value and operating principle: even subject-matter experts should approach problems with a beginner’s mind. The follow-up: “so you’ve got to get going.” Biases toward action and experimentation.
  4. Building in public as radical trust-building. Not radical transparency, but showing the humans behind the product — meetings, decisions, team members. The intention: restore trust that was lost in the tech industry over the past decade.
  5. The internet computer. The long-term thesis: everything in computing is moving to the internet (applications, files, compute). The device becomes an empty shell. The browser — or successor interface — becomes the computer. Arc’s aspiration is to be to the web browser what the iPhone was to the cell phone.

Optimise for feelings

“None of us are here for that. We’re there to make people feel something.”

Josh’s argument: the best-loved consumer products (Nike, Disney, Apple) were not designed by optimising a metric. Walt Disney was not asking, “What is our OBPS?” (On-platform Behaviour Per Session — a real metric from Josh’s time at Facebook).

The practical operationalisation: in project discussions, the team asks what feeling they are trying to create. For the Peek feature (hover over a link, it opens temporarily without losing context), the target feeling was “light and airy” — effortless context switching. That target guided the interaction design.

Metrics remain useful as a reality check — D5/D7 retention (how many users open Arc 5+ days a week) tracks whether the emotional engagement is real. But metrics are a tool, not the goal.

Hiring philosophy: heartfelt intensity

The Browser Company’s most important value. Not “we obsess over details” (a generic corporate value) — but “you show up with something to prove.” For each person it is different: UI craft, engineering performance, a vision for computing.

Josh’s interviews are deliberately unusual: “Ask me anything.” What the candidate chooses to ask, and how they follow up, reveals who they are more than answering a prepared question.

Notable hires who took IC roles after senior leadership positions elsewhere:

  • The engineer who built the first version of Chrome and ran it for 16 years.
  • The first designer at Tumblr, later SVP of Design at Slack.
  • A senior director of engineering who was SVP of Product at Vimeo.

The common thread: they came to do their career-defining work.

Culture: assume you don’t know

A prototype-driven culture. The “assume you don’t know” value deliberately creates beginner’s mind. Paired with “start by asking what could be” — pushing for ambitious aspiration before settling on a solution.

Company values emerged organically: Josh interviewed every team member about what they loved about The Browser Company, extracted the common threads, and wrote them as a fictional road trip essay (“Notes on Road Trips”) rather than corporate bullet points. The framing: an essay about a person and their father taking a road trip, as a vehicle for encoding how the company works.

Unusual teams:

  • Membership team — full-stack owner of the relationship with every Arc user, from first contact through ongoing use. Combines customer success, user research, and feedback loops in one role.
  • Storytelling team — full-stack owner of The Browser Company’s external narrative: press, marketing, social media, video. Three people; deliberately diverse backgrounds (The Verge reporter, Snapchat marketing, indie filmmaker).

No PM organisation: the PM verbs are distributed to whoever is best suited for each project. An infrastructure engineer leads performance projects; a membership team member leads some product projects.

Building in public

Arc operates as an experiment in trust-building. Josh’s rationale: the tech industry has lost the trust of users over the past decade. A great privacy policy is not sufficient. Making the humans behind the product visible — imperfect, average-looking, genuinely earnest — is the counter.

The specific risk Josh worries about: the founder becoming too central to the story, producing CEO-hero worship rather than team visibility. He deliberately highlights team members publicly when features ship.

The internet computer thesis

“We want Arc to be the iPhone for the internet.”

The argument:

  1. Everything is moving to the cloud: applications are URLs, files are on cloud servers, devices are becoming empty shells.
  2. In five to ten years, smashing your device loses nothing — everything is already out there.
  3. The interface to this cloud-native world will become more important than any individual device.
  4. The current browser companies (Google Chrome, Apple Safari) have incentives that conflict with making this interface as powerful as it could be: Google wants indexable content, not immersive web apps; Apple wants native App Store apps, not web apps.
  5. The Browser Company, without these conflicting incentives, can build the true interface to this internet computer: as native-feeling and immersive as a desktop application, but on the open web.

The developer platform implication: if Arc becomes the dominant interface, the developer platform built on top of it becomes the most valuable layer — analogous to how iOS App Store became more valuable than the iPhone hardware itself.

See also