Feature Request: PWA

[farribeiro]

https://web.dev/progressive-web-apps/

[vwkd]

I think this issue confuses PWA with just being responsive.

[frostedkitsune]

I think this issue confuses PWA with just being responsive.

I think so PWA and responsive design are two different things....btw, what is the progress on any of this topic?

[C0ffeeCode]

This might be interesting regarding this issue:
https://developer.mozilla.org/en-US/docs/Web/API/Badging_API

[RihanArfan]

PWA will allow Cinny to be installable on desktop or mobile and make it feel like a native app. Other things can be done like full offline support so it loads fully from the cache.

This might help. https://create-react-app.dev/docs/making-a-progressive-web-app/

[reesericci]

I would like to see PWA support, as then I could use Cinny on my phone like a native app.

[Iruwen]

I assume we need a PWA service worker to get true push notification support on mobile besides caching, so this would be a killer feature.

[C0ffeeCode]

I had been working on implementing background notifications using service worker, but it requires changes to how Cinny saves the token since localstorage, where it lives today, is not available in serviceworkers, so it would have to be migrated to indexeddb.
If someone is interested to take it over:
https://github.com/c0ffeecode/cinny/tree/background-notifications

It takes advantage of push gateways and ntfy, so it can listen for notifications using WebSockets efficiently.

As for the Tauri build, it propably would be better implement background notifications in rust.

[genofire]

@C0ffeeCode it sounds you do not use VAPID WebPush Notification for this insteat:
https://support.mozilla.org/en-US/kb/push-notifications-firefox

Like hydrogen-web it does: https://github.com/vector-im/hydrogen-web

[Iruwen]

By its description it doesn't sound like there's an "instead" due to its severe limitations.

[rltas]

Looks like it'll become much more useful "soon":
https://webkit.org/blog/12945/meet-web-push/
https://firt.dev/ios-15.4b#web-push-notifications-on-ios%EF%BC%8Dwith-a-catch

[genofire]

See also #867 for non web

[RihanArfan]

Now that we're using Vite, we can use Vite PWA. https://vite-pwa-org.netlify.app/frameworks/react.html

[jasikpark]

web notifs nearly work today on iOS Safari 16.4, except there seems to be a bug in the notif system, where it doesn't think it does have perms?

I have #1231 up to fix the rendering issue, though since there's not a service worker, that PR doesn't fix iOS notifications

[jasikpark]

https://elk.zone is a good example of a PWA w/ web push on iOS: https://github.com/elk-zone/elk/blob/e9740fe693cfec761cce69d47d25dc98825d0ce2/service-worker/web-push-notifications.ts#L4

[jasikpark]

https://developer.apple.com/documentation/usernotifications/sending_web_push_notifications_in_web_apps_safari_and_other_browsers

[NovaAndrom3da]

I would love to have proper iOS notification support, that seems to be the only thing I'm missing

[filipesmedeiros]

This is a low hanging fruit if we just want to enable installation, basically just add a web manifest, right?

[MulverineX]

Features like offline support & web push integration would be great, but yeah just getting the manifest and a dummy service worker in so installs are possible would be great. ( @filipesmedeiros simply adding the manifest isn't enough, browsers will refuse to install the PWA if there is no service worker present )

[filipesmedeiros]

@MulverineX that sounds right. Still easy just to enable installation, imo eheh

[RihanArfan]

Features like offline support & web push integration would be great, but yeah just getting the manifest and a dummy service worker in so installs are possible would be great. ( @filipesmedeiros simply adding the manifest isn't enough, browsers will refuse to install the PWA if there is no service worker present )

Now that we're using Vite, we can use Vite PWA. https://vite-pwa-org.netlify.app/frameworks/react.html

Vite PWA can take care of all of this for us. I'm not familiar with React, otherwise I'd submit a PR to implement it.

[likeazir]

So, I really wanted to use cinny on mobile with true reliable background notification support, so i looked into fcm webpush and hacked some crude notifications into the app.
However, I have never touched javascript or anything web related before so it's really messy at the moment and very much work in progress.
Maybe I'll do a PR when I have the time to clean it up and do it properly.
Just putting it out there if someone else is working on this :)

[williamkray]

So, I really wanted to use cinny on mobile with true reliable background notification support, so i looked into fcm webpush and hacked some crude notifications into the app. However, I have never touched javascript or anything web related before so it's really messy at the moment and very much work in progress. Maybe I'll do a PR when I have the time to clean it up and do it properly. Just putting it out there if someone else is working on this :)

you, uh, had any time to put this somewhere that someone else could see it by any chance @likeazir ?

[likeazir]

notification

@williamkray as far as I could tell, proper support would involve putting lots of the matrix code into a service worker to decrypt the notification.
Even when I settled for not decrypting notifications, I ended up with a mess. So unfortunately this is not something I can do at this time.

[ilar]

Why not just display that there WAS a message, for encrypted messages? That's what Cinny does on desktop, and would at least make for MVP release. Since most people that are big into E2EE stuff probably wouldn't want their notifications leaking information anyway, decrypting the notification to see what it actually was would be a low priority.