Polypane, The browser for ambitious web developers
polypane.app
polypane.app
Happy to answer any questions folks have!
The password has to have:
- At least one lowercase letter
- At least one number
- At least one uppercase letter
- At least 8 characters
I do not like it when websites (or applications, w/e) do this. I am somewhat OK with "at least 8 characters long" and I even understand its significance (from a security perspective) but not the rest.
Computer: Apple M3 Max
macOS: 14.7.3 (23H417)
Google Chrome 134.0.6998.118
I also tried in my "clean" chrome profile (to rule out extensions) and it's still got really bad scroll lag. This happens as soon as I open the page.
Here is a video though I understand it's hard to convey since you can't see when/how much I'm scrolling. I can tell you I scrolled slowly down and back up consistently through this video.
https://cs.joshstrange.com/m71YtZdk
Even worse, I just found that having that tab open (and visible) makes Chrome (no other app) laggy everywhere. Something is definitely wrong with that page. Also that page was open in a different chrome profile and it still made my main chrome profile lag when just trying to click around the text area for this comment on HN.
Edit: Some extra details for my setup, I have external monitors (4) and the Macbook Pro is closed in clamshell mode. Not sure why either of those things would matter but I figure both those cases are more common for people on HN (external monitors/closed laptop) than the general public so I wanted to mention it.
Edit2: And here is a video of me doing the same scrolling on the homepage just to show the difference: https://cs.joshstrange.com/GWLr0Qwl
Glad to see a productized version! Most of my work these days is for internal tools with fixed browser expectations, otherwise I'd probably be downloading a trial right now.
Congrats!
I had a title stating that for the longest time, then I noticed nearly all other landing pages simply have it without title and just a clean list of logos, so I changed it to that as well.
Pretty misleading and underhanded I think.
Not to take away from the product, which does look cool, but the “customer list” is definitely sketchy.
Polypane made a massive difference in getting our startup's website shipped a few months ago. I highly recommend it for entrepreneur-devs.
> On Mac, Window and Linux
should be
> On Mac, Windows and Linux
At least the icons are right!
Is there some sort of middle ground? Say, minimum purchase cost is the same price as six months, but it keeps on working afterwards sans updates. When the dev realizes that such a tool is only 80% effective unless it is totally updated, they can subscribe.
So there's two reasons:
1. The only way to do that continuous upkeep of the rendering engine that I have found to be sustainable is with a subscription.
2. I definitely don't want to be responsible for people using years-old versions of Chromium.
If you happen to work in such an environment you have vastly different considerations from the other 99% of developers building websites and apps on the public facing web.
Sounds like a bit of a hassle on the logistics/release engineering side, though. That would need to be handled with some care and planning.
[0] Which I'll admit I don't 100% buy, but I'd love for a security expert to weigh in.
By design, you'll have users spread across any number of versions. And you have to decide how far back you're going to issue updates. And instead of having nice in-app updates and a policy of "just upgrade to the latest version", you have a system that's complicated for you and your users. And you have to decide if you're okay letting users use (by design) releases with issues that have long been fixed.
I can see how Adobe and Jetbrains have the manpower to do it, but a solo dev or a small team, you should spend your time building the dang product rather than appeasing people who don't think your product is worth $9/mo.
I've heard plenty of arguments on the 'financial tools to manage them are bad' (forget about them, hard to cancel) but few against 'paying money proportional to how much I use the product'. As a general concept that seems reasonable to me - if you use a product for 10 years, it's fair to pay more than somebody who uses it for a couple of months.
In a world where finance improves (more subs via Apple Pay et al, more banks like Revolut that show & allow unilaterally blocking any given recurring charge) would you still avoid them?
- It's hard to convince my boss to create a subscription.
- I don't want to become hostage to monthly payments - if I don't pay one month my whole workflow is messed over, so I have to continue (vs. otherwise I can slowly trade it out of my workflow, and/or look for alternatives)
- Its hard for me to mentally grok how much I am paying monthly on subscriptions.
- I never cancel, because inertia.
- I am not sure if this is something that justifies a monthly subscription, and two weeks is too little time for me to invest in changing my workflow to accommodate it.
- I hate subscriptions (this is an emotional thing, so you could tell me to get a shrink. But I suspect I am not the only one).
I feel like I am missing even bigger reasons, but /rantPlot twist: their "app" is just the same site wrapped in a webview, minus the nags to install the app.
For devices:
- user agent
- reported platform
- device pixel ratio
- rendering mode (mobile rendering and desktop rendering respond differently depending on your viewport meta tag)
- default input device
- orientation APIs
Beyond that it can also emulate reading direction, page language, browser locale, user-configured default font-size, different network settings and a whole range of different media queries like color-scheme, reduced-motion reduced-data, reduced-transparency, prefers-contrast, forced-colors (windows high contrast mode) and color gamut. I'll be adding even more device browser-specific emulations later this year.I don't have a list of differences off the top of my head, but I regularly find big enough differences that I don't rely on "responsive mode" or even (as mentioned) Apple's iOS simulator (because it does not accurately replicate the real on-iPhone browser rendering, which has bitten me before).
So yeah, you should be testing (mobile) Safari and Firefox too. Chrome on android has some different APIs compared to Chrome on desktop, but rendering is identical.
When developing your site, you can use Polypane Portal[1] to tunnel your local site to real devices while keeping them fully in sync with what you do in Polypane, so you can scroll, interact, inspect and even edit across real devices from inside Polypane, saving you a ton of time.
And only polypane that dont support other engines then also don't work.
It does however minimise that device testing time. So it all depends on how valuable that time is for you.
It looks like it's built off chromium, so I'm assuming it wouldn't be able to show an issue that only appears in safari or maybe Mozilla?
Perhaps this is in the docs.
edit: It's in the FAQ at the bottom. Still, beyond the actual browser engine, are there other known limitations?
Polypane doesn't simulate the specific rendering engine of other browsers, it just pretends to be another browser (which is what emulation is) so you can test that the code you wrote for those browsers (for example, a polyfill) responds well. You'll still need to test in those real browsers to check against their rendering bugs or support gaps. (but something like Polypane portal[1] can make that step much easier)
Maybe I am not getting it. I am probably not getting it.
I've been playing around with it for a few minutes and I think what I'm really appreciating is that it's filled with dev tools of all kinds and it's really optimized for working on web sites rather than browsing. It can automatically open panes based on CSS breakpoints, and it has presets for many devices. Some of it is things I had in Chrome, but better, like rulers and guides and grids. Even the way screenshots are implemented shows they put thought into saving time and hassle over a thing you could of course do before with a few more steps. And it's not all related to layout: it shows meta tags and icons and previews for social media sharing.
Anyway, it's pretty cool IMO and I'll probably end up buying it if I keep working on web apps. The only downside I've noticed is that it feels a little sluggish, even when not heavily loaded down (e.g. just 3 panes). I'm using this monster M2 Ultra Mac Studio so it's a bit unusual for a browser to lag.
People here, out of all places, should be aware of what it means when a product is free.
What I appreciate:
- Session management keeps my workflow organised.
- Responsive-first design, with panes for both desktop and mobile views.
- Comprehensive screenshot functionality, including annotations.
Sure, you could replicate these features with other browsers or plugins, but I prefer having everything set up out of the box—one less thing to configure.
The support is outstanding. I encountered an issue with my IDE not launching Polypane correctly, and after reaching out on Slack, Killian helped resolve it quickly.
Reading through the Slack conversations, it's clear he's dedicated to building the best possible product for his users.
* Do you offer GenAI integrations? (Copilot, Claude, etc)
(Help me sell this to my manager)
Browserstack is an online device testing tool where you check if your site works on different real devices one-by-one. That is to say, they don't really compete: if you don't have real devices to test with then Browserstack is an excellent option.
What users mostly find is that by using Polypane (fast, local) they have far less use of Browserstack (slow, online) and the entire process speeds up. There will always be a need for real device testing.
There's no gen AI integrations, and I don't have any planned. You can happily use Claude or CoPilot in the browse panel though (which is a little browser that lives inside Polypane, so you can browse without losing the context of your project)
I tried using Polypane, but unfortunately, I couldn't find any relevant settings.
That’s not surprising, though Chrome DevTools doesn’t support it, and even the Safari simulator lacks this functionality.
It seems I still have to rely on guesswork and iterative adjustments to resolve all the issues related to safe-areas.
Have you seen the state of the (lack of) competition in browser markets these days? Even Firefox (via Mozilla's new EULAs) has stopped caring about your privacy.
More competition in the browser and browser tooling space is absolutely warranted.
And even then the homepage only lists about 30% of what Polypane does.
Besides the multi-pane synced windows I don't really see a new feature here. It's a lot of advertising of little-known features that are already built-in to Firefox
I'm not trying to shit on your product. It seems polished and possibly useful. It just seems insincere for you to advertise browser features that are built in as features of your app specifically
Sorry but I honestly don't understand this line of reasoning. Advertising a product having a feature in no way means claiming other products do not have the same or similar features.
I could list dozens of things not in Firefox, Chrome or any other browser that Polypane has (and in fact, you list off a few that definitely aren't in Firefox. ) but even so, listing the features a specific product has is the whole point of a marketing website.
Do you also expect Apple to list HP and Acer laptop alongside their Macbooks because those also have screens and keyboards, or otherwise it would be insincere they advertise (on their own marketing website) the screen of a Macbook?
My all products JetBrains subscription is £137 a year, for every single product they create (and perpetual fallback licences). This is £91 a year, which is about 66% of the cost of my JB sub and if I stop paying, I assume PolyPane stops working.
> Responsively App is built on top of Electron and uses Chromium as its rendering engine.
Now I want an app that shows Firefox, Chrome, and Safari side-by-side (besides manually opening them all side-by-side of course).
There's a huge list of things Polypane emulates beyond the screen size.
For devices:
- user agent
- reported platform
- device pixel ratio
- rendering mode (mobile rendering and desktop rendering respond differently depending on your viewport meta tag)
- default input device
- orientation APIs
Beyond that it can also emulate reading direction, page language, browser locale, user-configured default font-size, different network settings and a whole range of different media queries like color-scheme, reduced-motion reduced-data, reduced-transparency, prefers-contrast, forced-colors (windows high contrast mode) and color gamut. I'll be adding even more device browser-specific emulations later this year.Sorry JUST remove the word ;)
This is just a different approach. Provide a product (a browser), charge people that want that product.
Imagine someone came out with a browser that synced and allowed you to view/test your app in the days of ie6/7/8/9 across all those browsers. Would charging money per month for that be so weird?
This isn't for anyone to use as their normal browser.
So...software developers who mimic the real world. If I walk by a fruit stand, a grocery store, or a booth at a fair selling homemade crafts; I don't expect anything to be free. It is the exception when they are handing out free samples.
In the software world, too many expect everything in the store to be free (as in beer). Each software product represents real effort on someone's part, so it is not insane to expect them to want some compensation for that.
With software development the only thing lost with giving it away for free is the opportunity cost that someone might have paid for it.
So I don't think physical products and software can be compared like that
That doesn't change that they're different in reproducibility...
All these years where megacorps gave people stuff for free have tainted the minds of many.
If you questioned the subscription model over the perpetual license, that would be somehow acceptable, but assuming everything must be free is just non sense.
They are making lots of money with a very useful and nice-looking tool.
What's your excuse?