There was a downtime yesterday, and on my phone, the PWA showed a Gateway time-out page. The problem is, after the downtime was over and the site was backup, the PWA continued showing that time-out page until I quit and restarted the app.

While I eventually figured it out and now know to do that after a downtime, I'm worried that visitors who are on their phone may not know that the downtime is over, and may not know that they have to quit and restart the PWA in order to resume browsing my site.

Im not sure what we can really suggest on that. Essentially, the page needs to be refreshed somehow. Of course, quitting the app will do that. There isn't any way around that I dont think, as its simply how PWA apps work. I'll tag developers anyway to see if there are any suggestions of course

Thanks Marc.

3 minutes ago, Marc said:

I'll tag developers anyway to see if there are any suggestions of course

Could you not bring pull to refresh into PWA’s, would that still work in these situations?

The new refresh button on the menu bar does what it says on the tin, for the real app like experience, the pull to refresh is more natural for iOS users.

It's more likely a caching issue, I'm sure we can improve it by ignoring the cache if we get specific header codes.

8 hours ago, Day. said:

Could you not bring pull to refresh into PWA’s

That would be amazing if that could be implemented.

https://developer.mozilla.org/en-US/docs/Web/Progressive_web_apps/Tutorials/js13kGames/Offline_Service_workers

I'd like to suggest implementing a Service Worker to improve user experience when the server is temporarily unavailable (e.g. due to maintenance or unexpected issues). Currently, when the server returns error statuses like 503 (Service Unavailable) or 502 (Bad Gateway), users are faced with a default browser error message, which is not informative and lacks branding. We can use a Service Worker to intercept network requests and serve a custom "Offline" or "Maintenance" page when these types of errors occur.