The point isn't showing what they look like, it's that the result is randomized. Screenshots aren't, so that kind of defeats the purpose.
The article starts with instructions on how to actually see and interact with the demos (the easiest is to use https://polypane.app ), as well as a video showing all the demos from the article running in Polypane.
Personally, I've found that just moving the screen out of the sun (for example by turning it upside-down, or holding my hand in front of it) when refreshing a page is enough to prevent it.
The wallet app UI is the peak of Apple's 'single 20y/o in sf' design.
Anyone that has multiple card from the same bank (because, say, you have a personal account and a shared account with your partner) has to do the "pick between the two identical looking top 20px of cards" dance every time they use Wallet to pay for something. It is mind-boggling that the current UI persists.
Hey, Polypane founder here hoping to get feedback and iterate ;)
Needing to fill in the paperwork for a saas is a PITA. Is there anything I could add to the site or elsewhere that would have made that easier for you?
This is strongly in tin-foil hat territory but: streaming video costs a lot more money than streaming some JSON to populate a UI. Every minute you spent browsing the catalogue over playing a video is probably a significant costs saving for Netflix.
This reasoning misses a very large portion of Polypane, which is that you use it while developing, not just testing. It's a replacement for your time in Chrome/Firefox/Safari, not your time testing across devices (real or through online tooling like Browserstack).
It does however minimise that device testing time. So it all depends on how valuable that time is for you.
Sure. Chromium is an evergreen browser, which means it's continuously patched and updated in the background. Getting a pinned Chromium version takes quite a lot of work, and really only happens in very specific, controlled environments.
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.
> 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?
I don’t see how you can come to that conclusion with even a superficial reading of the homepage, unless you count ‘shows web pages’ as ‘almost all features’.
And even then the homepage only lists about 30% of what Polypane does.
Those are customers. Just like for example on netlify.com.
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.
Polypane is a chromium-based browser that you install on your own device and use while building applications that lets you develop at different (emulated) devices and screensizes/variation in one overview, with a bunch of development, accessibility and quality tools built right in.
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)
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)
The article starts with instructions on how to actually see and interact with the demos (the easiest is to use https://polypane.app ), as well as a video showing all the demos from the article running in Polypane.