Add recommendations for mobile clients #1915
Conversation
Signed-off-by: Guido Günther <[email protected]>
There was a problem hiding this comment.
I think this may go better under https://spec.matrix.org/v1.11/client-server-api/#receiving-notifications.
@matrix-org/rust could I confirm whether this is the best practice for mobile developers to receive (non-)encrypted events?
|
|
||
| In order to save bandwidth and battery mobile clients should: | ||
|
|
||
| - Use [push notifications][/client-server-api##push-notifications] to get notified about new events |
There was a problem hiding this comment.
| - Use [push notifications][/client-server-api##push-notifications] to get notified about new events | |
| - Use [push notifications][/client-server-api#push-notifications] to get notified about new events |
|
|
||
| - Use [push notifications][/client-server-api##push-notifications] to get notified about new events | ||
| - Disable continuous `/sync` calls | ||
| - Fetch the events indicted in the push notifications via the ``GET /rooms/{roomId}/event/{eventId}`` API call |
There was a problem hiding this comment.
| - Fetch the events indicted in the push notifications via the ``GET /rooms/{roomId}/event/{eventId}`` API call | |
| - Fetch the events included in the push notifications via the ``GET /rooms/{roomId}/event/{eventId}`` API call |
There was a problem hiding this comment.
Also, could you linkify GET /rooms/{roomId}/event/{eventId}? Likewise with /sync?
Yep, something like this. For what it's worth, instead of using |
|
This feels like it has stalled. @agx: are you able to make the requested changes? |
Yes, I hope to get to this in the not too distant future. |
This came out of a discussion at https://matrix.to/#/!XXSJTvRPInupfUgQVb:matrix.org/$IUx1flZV7iLWIviEeJWrmIw8LHgv4DhKGDKnO1hU688?via=pixie.town&via=matrix.org&via=element.io
When looking into adding UnifiedPush support to a client I was looking around for RFC style "Best Comon Practice" implementation hints but couldn't find any. Maybe it makes sense to add something to the documentation? I couldn't find a more sensible place than the spec if there is one please point me to it?
Pull Request Checklist