4 Lessons Web App Designers Can Learn From Google 4 Lessons Web App Designers Can Learn From Google Suzanne Scacca 2020-08-12T10:30:00+00:00 2020-08-12T20:04:37+00:00 Whenever I’m curious about what more we could be doing to improve our users’ experiences, the first place I look to is Google. More specifically, I go to the Google Developers site or…Details
You don’t have to use Adobe Photoshop on your Mac to edit images like a pro. There are plenty of Photoshop alternatives for Mac that you can download or use in-browser to create just the right images and graphics for your projects. And some of them are completely free! None of these are necessarily one-size-fits-all…Details
I’m going to talk about something controversial today. Everyone strap in and brace yourselves. Freelance designers like to encourage newbies entering the industry to learn as many skills as they can to make themselves attractive as a job candidate. This is well-meaning advice that undoubtedly comes from a good place. But generally speaking, these ‘generalists’…Details
What comes first: branding or strategy? It’s an age-old question for designers and marketers and today extends to digital marketing as well. Should your brand design be based on digital marketing needs? In today’s marketplace, the answer is overwhelmingly yes. You’ll be hard-pressed to find a brand that isn’t leveraging some type of digital marketing,…Details
It seems like every designer and developer out there is on the hunt for perfection. As if somehow that’s our ticket to the top. The distinguished projects, the big paycheck and the booming business. It all will come if we just…do the impossible? The trouble is, we mere mortals aren’t known for perfection. Sure, subjectively…Details
Today, we’re talking about Serverless architectures. What does that mean, and how does it differ from how we might build sites currently? I spoke to Chris Coyier to find out. Show Notes Chris’ microsite The Power of Serverless for Front-end Developers Chris on Twitter ShopTalk Show podcast Weekly Update “Setting Up Redux For Use In…Details
Smashing Podcast Episode 22 With Chris Coyier: What Is Serverless? Smashing Podcast Episode 22 With Chris Coyier: What Is Serverless? Drew McLellan 2020-08-11T05:00:00+00:00 2020-08-11T08:06:06+00:00 Today, we’re talking about Serverless architectures. What does that mean, and how does it differ from how we might build sites currently? I spoke to Chris Coyier to find out. Show…Details
As developers, we like to use tools specifically made to make us as efficient as possible. We excessively research and get the perfect keyboard, our code editor or IDE is carefully picked and uses the perfect coding theme and coding font (Fira code, in my case). We have workflows to optimize our CSS and images and our build tools are optimized to do as much as possible as fast as possible.And then we use the same browser that everyone else uses to like cat videos on Facebook.
Isn’t that weird? We pick our code editor specifically out of dozens available; our keyboard has the perfect clickiness for our fingers; yet we use the same browser as everyone else. Just like we’re not using Word to write code just because everyone uses Word to write things, we shouldn’t accept using a regular browser to build websites.
This article is part of The Roadmap, where we look at the creation and promotion of products from the developer’s perspective. We’ll share top lessons from product leaders, and give technical founders a space to share their early-stage products with you. If you’re interested in being featured, let us know.
A typical workflow with a regular browser looks a little like this: Build the website on one size, then resize your browser and build the design for that. Then resize the browser again and build the design for that. Then … well, you get it. You’re doing it all one by one, repeating yourself over and over again. And if you’re unlucky, you get to do it all over a couple of times as you build, with new pages bringing new requirements that affect pages you’ve already finished.
And you may want to do more than just build the visual side of your page. Do you want to check your pages for accessibility as you go? Add a browser extension. Do you want to create a full page screenshot to send to your boss or client? Add a browser extension. Do you want to check that your meta tags are correct? You guessed it, add a browser extension. With just a few basic things you already need half a dozen browser extensions. Have you used a browser with half a dozen extensions? It makes IE11 look fast in comparison.
Polypane Works Differently
When you open Polypane, you don’t see just a website. You see your website at multiple screen sizes at the same time, just as if you had a bunch of devices on your desk. What’s better, though, is that all these screen sizes are synced: if you interact with one you interact with all of them, whether you’re scrolling, clicking, hovering or typing. You’re interacting with a single website; you just happen to see it at multiple sizes at the same time.
Seeing all the screen sizes side by side means you no longer have to resize your browser and go through them one by one. And those screen sizes are yours to pick: you can pick from over 20 pre-configured devices, like phones, tablets and laptop sizes or you can resize them freeform however you like.
Or you can ask Polypane to parse through the CSS of the page, find all the CSS media queries and create screen sizes from those, making sure you’re always testing the site on all the sizes you want to support.
This alone makes Polypane a massive productivity boost. But if you eliminate resizing your browser all the time, what else can we do?
Well, what about reloading?
Polypane works with any hot reloading or live reloading system, just like any other modern browser out there. But Polypane also has a built-in live reloading server that requires zero configuration. Just tell it which folder to check and you’re done. It even works with plain HTML files! And best of all, if you update a CSS file or image, Polypane just refreshes that instead of reloading the full page.
At this point you might ask: but what about developer tools? The developer tools that ship with regular browsers are amazing, and Polypane uses the same powerful developer tools as Google Chrome and Microsoft Edge (developer tool extensions included). But the developer tools in browsers are also an add-on as best. 99% of a browser’s target audience is non-developers, so we only really get this small box of developer tools as our territory.
But if we think of the entire browser as the developer tool, we can not only unlock much more new functionality, but we can also optimize it so each new function doesn’t slow down the rest of the browser like browser extensions do.
And that’s why Polypane has so many features built-in:
full page screenshots
live previews of what your page looks when shared on social media
built-in accessibility testing
dark mode and reduced motion media query emulation
live CSS editing in all screens
color blindness simulators
a side browser so you can show your handoff tool, documentation or design right next to your site
a CSS color contrast checker that suggests colors for you that you can then live-preview
image overlays for visual regression testing or pixel-perfect design
Advanced Testing Tools
And we’re just getting started. What about an element inspector that lets you edit your page in all screens at the same time and makes it really easy to test out new styles and content? That’s what the Polypane Element inspector lets you do.
No other browser lets you edit multiple screen sizes at the same time in such an intuitive and fast way. We also have panels that let you check your page’s outline (showing all the headers and their hierarchy), one that lets you edit all localStorage and cookie information, or one that lets you write CSS or Sass that then gets inserted into every screen for ultra-quick prototyping.
The overlays in Polypane let you quickly try out a wide variety of things on single screens, like emulating color blindness or other visual impairments, check your layout for issues or list all the z-indexes on a page.
All of these tools help you with different parts of developing your web page, and in research we’ve done with Polypane users we’ve seen that developers are between three and ten times as productive when they use Polypane, depending on the task. Furthermore, because Polypane makes it so easy to check things like meta information and all browser sizes, the amount of post-launch bug fixes drops dramatically.
In future articles, we’ll explore how to do a full website audit using Polypane, and how to build a responsive design from scratch using everything Polypane has to offer.
Polypane has a free trial that gets you started with 14 days to try it out.