I read the first couple of sentences, opened the link on my phone and found the experience a bit disappointing. Then I realised they're talking about a _desktop_ PWA, complete with a mimetype file_handler.

I know it's not that big a deal and the performance improvements in that PR are the real headline, but I personally really appreciate a well-executed PWA & seeing it headlined as such. Those features have been there for donkeys years, and it blows my mind how rarely they're taken advantage of properly - especially on the desktop.

Thanks for the feedback. I agree that the performance improvements are the biggest win here. The PWA support is essentially the starting point, bringing installation and file association. Next up, we'll tackle file save using the File System API (instead of relying on sending exported scenes to the Downloads folder). I'm also keen to implement an offline mode (via Service Worker) soon too. Almost all SuperSplat users launch it in a desktop OS...so the PWA testing was done there. But out of curiosity, what should we tackle to make the experience great on mobile in your view?

I don't think you need to - as you say, the use-case doesn't make sense on mobile. My comment was more in appreciation of your desktop-first PWA. Look forward to seeing where you take it.

Understood! As a little update, the PWA got offline mode support in v0.18.0. We're now adding improved file open+save support which should be done by the end of the week.