Freshrss: progressive web app

[qwertygc]

Hello

An idea it's implant progressive web app in fresh idea. Indeed, with the offline mode we can read without internet and we don't need to use third part app.

[Frenzie]

It would be nice, although given that there's a multitude of API-compatible clients out there I'd personally peg it at fairly low priority.

[PhieF]

Hi ! You could, at first, just put a manifest for us to be able to create standalone shortcuts, like nextcloud did ! even if we don't have an offline access

[Frenzie]

I'm curious, which browser lacks such basic functionality?

[madb1lly]

Hi all, I just suggested this is Framateam, thanks to @Frenzie for the link.

The benefit of a PWA would be that it can also store downloaded feeds and articles for offline viewing and would generally be lighter-weight than a "native" app. Also, PWAs are cross-platform, so can be deployed by any browser on any plaform that supports it, e.g. Android, Windows, iOS (I think).

Cheers :)

[Frenzie]

Unless you're taking a jab at Java, I think most clients are indeed native, not "native." ;-)

[madb1lly]

Hi @Frenzie, fair point, I wasn't clear - I just meant that I think the concept of native vs webapps is a bit old-fashioned when considering PWAs and current javascript engines, especially if WASM can be used in some way.

I was thinking about the possibility of a PWA for this a bit more and since for offline use Freshrss would need to have a way of storing articles - I think this may be with the DBs provided by the web browser but maybe it's possible to install others alongside, for a PWA to use. If it depends on the web browser PWA you'd need to decide which articles to store as I imagine you can't store as many with a PWA as you can on the web server or perhaps in a DB for a traditional app.

[Frenzie]

I don't think there are any relevant practical limits on a PWA. It might still be slightly more limited out of the box in which case it would ask for more space after reaching certain thresholds.