Most web developers end up with more than one browser. Your users run all of them, so you test in several, and you also need a daily browser that stays out of your way. Those are two different jobs, and the best answer for each is different.
Which browser for which job
| You need | Look at | Why |
|---|---|---|
| Check that a site works everywhere | Chrome, Safari and Firefox together | Three engines, three sets of bugs. Safari is the only way to test WebKit on a Mac. |
| The deepest DevTools and extension catalog | Chrome | The reference browser for Chromium debugging, with the full extension platform. |
| Many viewports side by side | Polypane or Sizzy | Commercial browsers built around responsive testing and many devices at once. |
| Chromium with vertical tabs and developer tools built in | Yalqen | Open source, with a command bar, phone view, throttling and request rules, and no account. |
| Vertical tabs, workspaces and split view | Zen or Arc | Zen is open source and built on Firefox. Arc has stopped getting new features. |
| Blocking and privacy without extensions | Brave, Orion or Yalqen | All three block ads and trackers by default. |
| An AI assistant in the browser | Dia | Built around an assistant that works with your open tabs, with an account. |
Test in more than one engine
Chromium covers Chrome, Edge, Brave, Arc, Dia and Yalqen. Safari runs on WebKit, which is also what most iPhone and iPad browsers use, and Firefox runs on its own Gecko engine. A page that works in Chrome can still break in either, so keep Safari and Firefox installed for checking your work, whatever you use day to day.
Where Yalqen fits
Yalqen is an open-source Mac browser on Chromium, so it renders and debugs the way Chrome does, with the full Chromium DevTools on ⌥⌘I. What it adds is the tooling around the engine, as commands you run from the command bar on ⌘L instead of panels you dig for:
- Phone view on ⌥⌘M, with DevTools closed.
- Per-tab network throttling and user-agent switching.
- Saved request rules that block, mock, redirect or add headers, switched on per tab.
- Dark mode and reduced-motion toggles, full-page screenshots and timed reloads.
It also has vertical tabs by default, ad and tracker blocking from the first launch, and no account. Every tool is described on the developer tools page.
Where Yalqen is not the right choice
- You need to test on WebKit or Gecko. Use Safari and Firefox for that.
- You need Windows, Linux or an Intel Mac. Yalqen is macOS 13+ on Apple silicon only.
- You need the latest Chromium the day it ships. Yalqen’s Chromium version follows Electron’s releases, which can trail Chrome.
- You need the full extension platform or sync between devices. Yalqen supports part of the extension APIs and has no sync yet. See extensions.
- You rely on many viewports at once. Polypane and Sizzy are built for that.
Compare in detail
- A Chrome alternative for web developers
- Yalqen vs Chrome, Yalqen vs Brave, Yalqen vs Firefox
- An open-source Arc alternative for Mac, Yalqen vs Zen
Try it
- Install Yalqen with Homebrew or the disk image. It is free and the source is on GitHub.
- Open a project on localhost and press ⌥⌘M for phone view.
- Press ⌘L, type
>and look through the developer commands.