4 ms·
I ended up setting a web interface (converse.js) primarily for use with iOS. No push notifications with it, but also heard that iOS native clients tend to crash
by defanor 6y ago
I ended up setting a web interface (converse.js) primarily for use with iOS. No push notifications with it, but also heard that iOS native clients tend to crash and lose messages, and apparently can't run in the background.
- MattJ100 6y agoiOS doesn't let any apps run in the background. That's "fine" though, because the app can receive push notifications via Apple's push service, and that wakes up the app when you receive a message. That's supported by practically all public XMPP servers these days.
- arendtio 6y agoWell, what is not fine though, is the fact, that Apple neither allows other browsers on iOS nor implements the 'Push API' for Safari. This combination makes it impossible to build a chat apps using web technologies (which would lower the effort for building a client quite a lot).
- MattJ100 6y agoYeah, I agree that there are many things not fine about mobile push notifications in general. Hence the "" quotes in my previous comment :)
- aidenn0 6y agoI tried setting up a web-interface and I think converse.js was the least bad. It was still not great; had some issues with group chat bookmarks (I guess there are two standards?) chat-secure and monal both were very marginally better IMO.