Back in 2024 MDN surveyed web developers on the ability for web apps to be a replacement for native apps. Here's what they said: github.com/web-platform...
Rick Byers
Rick Byers
@rbyers.net
Web Platform engineer at Google on the Chrome team, helping the open web to thrive. Opinions are my own, not my employer's.
640 followers183 following210 posts
Rick Byers reposted
This is the best explanation of the interplay of specs, tests, and implementations that I've read. The point of both specs and tests is interoperable implementations, but that doesn't mean that implementations are always right when they agree.
My colleague @atbrakhi.bsky.social wrote a nice, cleverly titled post based on a very short exchange we had on Instagram the other day... www.atbrakhi.dev/blog/browser...
Happy 25th birthday @igalia.com. I am so inspired by the lasting value you have contributed to the web and society at large, and even moreso by your unwavering values in implementing that work. Here's to the next 25 years indeed! www.igalia.com/2026/09/21/T...
Rick Byers reposted
🎙️ New Episode of Igalia Chats Join the party and navigate the Origin Trial Google's Johnny Stenback and @rbyers.net join @meyerweb.com and @bkardell.com to chat about Origin Trials www.igalia.com/chats/origin...
I finally know what caused me to have to cancel my BlinkOn 4 trip four years ago!
Four years ago I missed my favourite conference ("BlinkOn") for a bad cold. It's been the biggest frustration of my lab that I couldn't find the virus that caused it. Now, that I have a 32-way panel from YouSeq.com I finally know why: It was a bacteria, H.Influenzea, not a virus at all!
I'm so impressed and inspired by the team relentlessly pushing and innovating to keep Chrome users safe from vulnerabilities: blog.google/security/chr...
Rick Byers reposted
🎙️ Check out Bruce Lawson’s interview with Alex Moore, executive director and co-founder of Open Web Advocacy. They explore OWA’s history, why it exists, and what it’s fighting for: a better, more competitive web 🌐✊ open-web-advocacy.org/blog/bruce-l...
Vibe coded a demo of the new navigator.cpuPerformance API in Chromium: rbyers.github.io/cpu-performa.... It's a small thing (returns just 0-4), but for some powerful web apps I think it'll be super useful. Details: github.com/WICG/cpu-per...
CSS Quake (cssquake.com) - no canvas just HTML/CSS using a cool library called PolyCSS (polycss.com). 😀 Playing through the first level brought back a lot of memories. I think I was one of the first to reverse engineer the PAK file format and build an editor days after the game came out.
Given how Chromium and WebKit are always vying for the top spot in Speedometer on MacOS, it's really striking how big the gap is on iOS! And we haven't even really tried to optimize performance for that platform yet! IMHO this is what you should expect to see when there's a lack of competition!
Here's something fun: I think my iPhone may have the world record Speedometer score for any iOS device? www.linkedin.com/pulse/test-d...
A great analysis! The punch lines: "The trend is clear: for every 100 milliseconds slower a store loads, conversion tends to be about 3.5% lower." "For every 32 milliseconds slower a store responds to interactions, conversion tends to drop by about 1.5%."
One of the most important pieces about web performance that I've ever worked on is finally live. After a few months of work, my analysis of the correlation between site speed and conversion across the entire @Shopify platform is out: www.shopify.com/enterprise/b...
Rick Byers reposted
Replying to @gordon.bsky.social
I think part of the phenomena here is that it is easy to predict things will fail: most things fail. So, stop energy is much cheaper to produce, because you would be right 99% of the time. Against-everything-for-nothing is a comfortable stance to take, but long term it is the 1% that move forward.
Just bought a new Razer mouse. Rather than install the native app, I had Gemini/Claude write a web app with the Web HID API, using the Linux driver as a reference. Less than 60 min of work laterand I think I'm done: razerweb.rbyers.ca It's a new world... Software on-demand!
Just bought a new Razer mouse. Rather than install the native app, I had Gemini/Claude write a web app with the Web HID API, using the Linux driver as a reference. Less than 60 min of work laterand I think I'm done: razerweb.rbyers.ca It's a new world... Software on-demand!
Rick Byers reposted
It’s fair to say that the V8 javascript engine runs on billions of devices today. And if you apply to this position on my team, you might get to work on it! Talk about impact!
Rick Byers reposted
An interesting lightning talk at BlinkOn about a little experiment @rbyers.net did -- 3 minutes to watch and share your thoughts! Very curious to hear them! youtu.be/b_R3o3VASjc?...
I'm excited about FedCM ambient UI. Balancing tough tradeoffs is one of the hardest things we do in Chrome and the only way to do it well is to experiment heavily and collect user feedback.
I'm putting together a chrome://flag in canaries that enables the FedCM's Ambient UX in the URL bar. I've been using it for a week or so: it is beautiful and I think it will have arrive at an economic equilibrium. Here is the before / after, how to enable it and why we are working on it:
Another day, another step down the path of our devices prioritizing their manufacturer's interests over the interests of the device owners. mashable.com/article/appl...
Rick Byers reposted
Chrome is announcing that they are moving into a two-week release cycle! Exciting bc the web needs to move quickly- resolving bug fixes, feature improvements, etc. It goes along with devops principles of shipping smaller, more frequent releases for stability developer.chrome.com/blog/chrome-...
How will agentic coding tools impact app platform choices? Lovable says: "web apps cost 40-60% less than native development and reach the market 50-70% faster." lovable.dev/guides/nativ...
Rick Byers reposted
6 years and 300+ experiments later, I've concluded that sequencing all the viruses going through my house is actually slightly useful, while still wildly impractical of course! lab.rbyers.ca/essays/20260...
Rick Byers reposted
Wow, I am constantly impressed by Google Antigravity and Gemini 3.5 pro. I used it to build a whole blog website, including totally custom Tweet archive, in just a few hours of work! Eg. see lab.rbyers.ca/posts/2024. Code at github.com/Rbyers/lab-b....
My talk at @henrihelvetica.bsky.social's SPDY meetup in Toronto is live: www.youtube.com/watch?v=xq2c.... It's pretty rough and unpolished, but I included some fun stories of the history of performance work in Chrome which you likely can't find anywhere else. Slides: docs.google.com/presentation...
The Chrome Identity and Payments team in Waterloo Canada is hiring several early/mid-career developers. I'm on the lookout for exceptional candidates with a passion for browsers and/or the identity/payments space! www.linkedin.com/posts/rick-b...
Rick Byers reposted
✨ Exciting proposal alert: the CPU Performance API. This proposal will add `navigator.cpuPerformance`, a value that measures the broad performance capability of the CPU. That way, we can scale up/down our animations to make sure everyone has the best experience possible for their device. 😄
I just almost made a dumb mistake. I've been enjoying Kurzgesagt videos for years (on various devices). After watching their video on AI slop I figured it was time to support them on a recurring basis, so I hit the join button... youtu.be/_zfN9wnPvU0?...
It was fun to be part of this, thanks Henri! I wasn't able to join the livestream for the rest today but really looking forward to listening to it over the next couple days!
✨ Core Web Vitals Summit ✨ stream is today in just over 1hr, @ 11am, virtual doors will likely open a few minutes before. Join us! Hang out. Come hear from web performance and ux professionals. 📆 TODAY, Wed Dec 3rd ⏰ 11a EST, 5p CET 🔗 bit.ly/cwv-summit
I think it's fair to criticize the Chromium project for apparently getting the initial cost/benefit prediction wrong on JPEG XL. But the fact that JPEG XL is moving forward anyway is a success to be celebrated in the consensus-forming process of the web platform! groups.google.com/a/chromium.o...
Now, if two engines have shipped a feature for an extended period and the third is still holding out, that's something to be suspicious of! We are always keeping an eye on the data to try to ensure Chromium isn't holding back interoperability. webstatus.dev/stats