Today, some colleagues and I kicked off a new series on developing Progressive Web Apps. It will run for 30 days and takes you from the point of knowing nothing about PWAs all the way through integrating some of the amazing advanced capabilities available to web apps today.
Building (and improving) PWAs in VSCode just got even better. Many thanks to the PWA Builder team for all their hard work!
Steve Faulkner offers a little more insight into how emoji show up for folks who rely on screen readers. And the results may not be what you expected.
If you’re at all confused about when it’s cool to use a div and when it’s not, this is the post for you.
Memory leaks suck and they proliferate when you slice & dice the DOM using JavaScript. Edge DevTools makes it easy to debug “detached elements” now.
Years ago we started thinking about how PWAs could extend their reach into the titlebar (like Electron apps can) and it’s finally a reality! Check out this deep dive from Patrick Brosset to learn how to do it with just a little bit of CSS and/or JavaScript.
Chidiebere Onyegbuchulem has assembled a huge list of awesome features that could work well for your Progressive Web App(s).
While working on tooling to analyze Web App Manifest usage in relation to some new feature proposals, it became clear we needed a test Manifest that included the proposed syntax for dark/light mode support. I decided to make this site the guinea pig and spent an hour or so tweaking things to make it happen. Here’s a run-down of what I did:
Since joining the esteemed group of editors maintaining the Web App Manifest spec for the W3C, I’ve been on the lookout for ways to enhance both web apps themselves—in terms of functionality—and how web apps are represented in app catalogs and digital storefronts. Some of that work is finally gaining traction and I’d love to get your input.
Testing JavaScript memory usage is not done often enough, but it’s incredibly important. This is an awesome guide from Tim Kadlec.