
Last week, The Browser Company released the first beta of its AI web browser Dia, but declined to discuss its features in any detail. It had provided some information about the browser back in May, and the factors that led to it creating Dia rather than moving forward with Arc. And I found a nice overview on Twitter/X that’s worth sharing. But now, finally, we have a better view of where Dia is going. And why.
“The question we wrestled with early on this journey was, ‘why would The Browser Company build a boring browser?'”, an email from The Browser Company reads. “How do you pair power with simplicity? How do you reinterpret creativity? What do you reinvent? When? And, maybe most importantly, why?”
The answers to those questions are provided by Charlie Deets, who was previously the design lead on Apple Safari and, before that, a product designer on WhatsApp and Facebook at Meta.
“In order to give people the space to explore Dia’s novel value, we needed to get out of the way with the browser,” he writes. “The first objective of Dia’s design is to allow anyone to switch to Dia at 10am on a Tuesday morning.”
What he means there is that Dia has to be familiar. It has all the core browsing features one expects from any browser, eliminating the central problem with Arc, which is that it was it complex and unfamiliar. Or, as it Deets writes, Arc “unapologetically innovates on core browsing mechanics like the tab bar, bookmarks, and tab groups.”
Dia is also “elevated,” he says, in that it adds “extra convenience and craft” on top of the familiar. These are small changes that “meaningfully shift the experience in aggregate.” Among those changes are the color of the current webpage extending up into the browser tab, fluid animations on the Assistant Bar and other UIs, the reimagined bookmarks bar, and its minimalist overall user interface. The Browser Company is trying to humanize the app to make it more approachable.
“Avoiding duplicative UI elements in the interface helps keep Dia simple and fresh in comparison to some of the more established competitors that support duplicative or legacy workflows,” he writes. “We tend to err on the side of minimalism in the core UI, even if difficult to achieve.” Here, he cites Dia’s lack of update banners, the bookmarks button that only appears when you hover over the URL, and changes to how profiles display based on whether they’re in use.
Dia also uses machine learning (ML) in the navigation bar so that the right thing–a Google search, an AI-based result, navigating to a website, or whatever–happens automatically.
“You get the result you were looking for without thinking: it just works,” he says. “This feature is critical to Dia’s experience and was again the result of close collaboration between engineering and design.”
Where Arc’s “novelty budget” was all spent on power user features, the focus in Dia is Chat. This is the real value proposition of this product, it seems. You can chat with the browser and get context-relevant answers. There are @-based ways to reference tabs, history, bookmarks and other browser features. You can ask questions across multiple tabs. There’s a sidebar for a more traditional side-by-side chat experience. And Chat has a Skills feature by which you can personalize the experience and give it additional capabilities. Dia’s coding and writing skills are built-in, and you create your own custom skills.
Looking ahead, Deets says that Arc features like sidebar tabs, tab management, and incoming link routing for profiles are coming to Dia, though they will be implemented in a way that respects the familiar and minimalist approach of the new browser.
“In the long run, our product strategy becomes less defined because we will need to adapt to the world and how people are using technology,” he adds. “Will a browser first experience be the right UI? Will the browser be an assistant to your Chat? We are going to pay very close attention to how people are using Dia and be unafraid to adapt quickly to new behaviors. We continue to assume we don’t know.” (The latter is a core tenet at the company.)
The big question he doesn’t address, of course, is when the majority of computer users–those using Windows PCs–will be able to give Dia a test run. I’m looking forward to that.
In the meantime, you can learn (a little bit) more on the Dia website.