11–20 of 178 posts
Earlier quoted context omitted.
> why do it as a PWA? Presumably, so that it can be available in his car, when there’s no network access.
I meant the site linked to here - it's done as a PWA when there was no need to, and it fails on first load on mobile Safari for some reason.
What happens to your PWA page weight when you add tracking and ads to it? How do I find your ad-free hobby project in the sea of search results for "speedometer" PWAs on the open web? What makes sure you will keep paying the, admittedly modest, hosting costs for the app? I think it's great you can make "tiny PWAs" but I think the article is glossing over the incentives and discovery problem that leads to 30MB ad-infe…
Hosting static content can be done for free. Looks like he's using Firebase, but I believe you could host it on Netlify/Github Pages for $0, since there's no server side work being done.
What happens to your PWA page weight when you add tracking and ads to it? How do I find your ad-free hobby project in the sea of search results for "speedometer" PWAs on the open web? What makes sure you will keep paying the, admittedly modest, hosting costs for the app? I think it's great you can make "tiny PWAs" but I think the article is glossing over the incentives and discovery problem that leads to 30MB ad-infe…
I thought the point of a PWA is that it is installed on the phone. So it doesn't need any hosting.
For the initial distribution, IPFS would be a good fit. It ensures a.) That even if the original developer is compromised you still don't get a malicious app, and b.) That even if the original developer stops hosting it, it's still available as long as anyone in the world is hosting it.
Earlier quoted context omitted.
Hosting static content can be done for free. Looks like he's using Firebase, but I believe you could host it on Netlify/Github Pages for $0, since there's no server side work being done.
Firebase has a pretty feature complete free tier.
Tiny PWAs and why they don't render until you force refresh on mobile Safari. Edit: to be slightly less snarky, that was my experience of the linked site - just one long scrolling blank page. This could be a really simple HTML / CSS page. Why do it as a PWA and add more points of failure?
The footer says it's based on Polymer and Hugo, perhaps they don't play along well with Safari?
Strange how Safari still has trouble with PWAs, web applications were one of the main selling points of the original iPhone...
What is a PWA?
I’m finally groking what rms has been banging on about for so long. It is completely unacceptable that we are running software that does this to the user. Users need to be empowered and able to run code that they can control.
Earlier quoted context omitted.
I meant the site linked to here - it's done as a PWA when there was no need to, and it fails on first load on mobile Safari for some reason.
Ah, right. I was confused because everything worked fine for me. Although, believe it or not, after reading this comment, I went back and saw the exact behaviour you describe! (Safari, iPad)
Earlier quoted context omitted.
> why do it as a PWA? Presumably, so that it can be available in his car, when there’s no network access.
I meant the site linked to here - it's done as a PWA when there was no need to, and it fails on first load on mobile Safari for some reason.
> “surely there is a app for that!” A quick look leads to speedometer apps with ads and 30MB download weight, and simple screen light that also have ads that weight in at 5MB. I’m finally groking what rms has been banging on about for so long. It is completely unacceptable that we are running software that does this to the user. Users need to be empowered and able to run code that they can control.