Marketing
Jun 27, 2022

Why We're Building a Hybrid Browser

We're excited to unveil Whist to the world. In this blog post, we discuss what we've built and why we've built it.

Why We're Building a Hybrid Browser

The first time I drove a hybrid car...

I was surprised to discover that it looked a lot like my old gasoline-powered car. Same dashboard buttons and leather-bound steering wheel. No spherical wheels or wing-tipped doors. As far as I could tell, the only difference was in the engine’s sound — a velvety whistle as opposed to a churtling roar.

But at the same time, I knew that this car was different. I understood that in order for a car to be powered by both gasoline and electricity, its guts and inner wiring had to have been overhauled. That while I drove, two separate drive systems and a computer were deciding whether the rear electric motor or the front gas engine should take over. 

At Whist, we think of today’s browsers as gasoline-powered cars. We’re building the next generation browser: a hybrid electric car for the web.  It’s a normal, native web browser that looks like Chrome but with one distinction: it supports both native tabs and cloud tabs.

This article introduces Whist to the world: why we’re building it, who it’s for, and how you can get involved.

What are cloud tabs?

Right now you’re reading this article on a native tab. A cloud tab is like a native tab, but equipped with a certain set of superpowers. It uses near-zero memory. It loads pages blazingly fast, especially slow web apps and dashboards. And it’s powered by a cloud GPU for an extra kick of power. If you have a lot of tabs open, your laptop might feel pretty hot. That won’t happen with cloud tabs.

Whist looks nearly identical to your current browser. The only difference is that it offers four interchangeable modes:

  • Ultralight: All your tabs are cloud tabs. Designed for people who hoard hundreds of tabs or run heavy, non-browser apps like VSCode. In ultralight mode, Whist is like a pure electric car.
  • Accelerated: Only certain tabs, decided by you, are streamed. Like a hybrid car, Whist runs as most sites inside native tabs and injects electric juice into heavy web apps when you really need it. 
  • Smart: Whist switches to cloud tabs only when it detects that your computer is running out of memory or processing power, like how hybrid cars only use electricity at certain speeds.
  • Native: No tabs are streamed – Whist becomes a fully native browser. Designed for areas with unreliable Internet like crowded offices or coffee shops, where streaming leads to undesirable user experience.

Why hybrid is better

When we founded Whist in 2019, we pitched the idea of a “Netflix for desktop applications.” We asked our investors to imagine a platform that streamed all your sluggish apps – photo and video editors, 3D and CAD apps, even Slack – from the cloud. 

Within a few months, we had removed all apps from our platform besides one: Google Chrome, which had garnered the majority of downloads. But it still wasn’t perfect, and we fielded countless user complaints about a browser that was fully streamed from the cloud:

  • In places with unreliable Internet like offices and crowded coffee shops, Whist would stutter and lag
  • Features we take for granted in a native browser, like camera/mic support during Google Meetings or support for multiple simultaneous browser windows, are extremely difficult to build when streamed
  • Certain websites block IP addresses originating from our servers. Amusingly, we discovered this when a user tried to buy clothes from Abercrombie, which blacklists most cloud IP addresses
  • Users greatly value the assurance of privacy that a local browser provides, especially for sensitive information like bank info or for incognito tabs
  • Running a single Wikipedia tab in the cloud wastes server resources

We asked ourselves: what if we kept the browser native, and instead only streamed individual tabs? What if we took all the things that make a native browser great and just made them better, instead of compromising on certain features in exchange for others?

A glimpse into the tech behind Whist

Like all great browsers built for performance, Whist is Chromium-based. Specifically, we built Whist on top of Brave due to their uncompromising stance on user privacy. In doing so, we have injected our streaming technology as patchwork on top of Chromium’s core.

Along the way, we’ve overcome some pretty challenging technical hurdles. To name a few:

  • GPU sharing among multiple containerized, graphical applications
  • Shaving the launch time of a container from minutes to seconds
  • Rewiring Chromium’s renderer layer to render native tabs and cloud tabs in a way that’s visually indistinguishable to the user
  • Ensuring that user data in cloud tabs is treated with the same level of privacy and security as data in native tabs

(If these solving problems like these sounds interesting to you, we’re hiring!)

What's Ahead

Our browser design philosophy centers around preservation: we aim to keep what’s great about Chrome while hyperfocusing on its core performance. To the naked eye, Whist will look and feel nearly identical to Chrome. The past two years have seen a flood of browsers that fundamentally transform Chrome’s user interface – unlike them, we are not in the business of moving around buttons, reinventing tab groups, or creating productivity workspaces.

On pricing, Whist is completely free, as browsers should be. As for cloud tabs, we’re debating between a premium add-on in the ~$10/month range or making them free altogether. Ultimately, the pricing model will come down to user feedback, how users utilize cloud tabs, and how many hours/month they use them for.

We can’t wait to unveil Whist to the world. Before we do that, we’re nailing every element of the user experience by carefully onboarding small groups of users. If you’re interested in trying us out, please request access and we’ll be in touch soon with next steps.

Related posts

No items found.