Skip to content
This repository has been archived by the owner on Jan 10, 2024. It is now read-only.

Alarm / notification system #9

Closed
kordianbruck opened this issue Feb 4, 2016 · 12 comments
Closed

Alarm / notification system #9

kordianbruck opened this issue Feb 4, 2016 · 12 comments
Assignees
Milestone

Comments

@kordianbruck
Copy link
Member

It would be great to have GCM on the iOS app as well in order to be able to support the Alarm feature on both platforms and maybe get better backing from the TUM through this.

The GCM message format is listed here: https://github.com/TCA-Team/TumCampusApp/wiki/GCM-Message-format

The GCM message does not contain all the information needed as that would probably exceed the size limit of the GCM payload. In order to fetch the full message please check the API client in the Android version.

screenshot_2015-11-05-18-20-03
screenshot_2015-11-05-18-14-23

@pfent
Copy link

pfent commented Feb 4, 2016

GCM on iOS can probably be implemented via https://developers.google.com/cloud-messaging/ios/client?ver=swift

@nerdsupremacist
Copy link
Member

Thanks!
I will start working on this right after the exams.
I'm still kind of fussy on the architecture of this thing and what role the TumCabe Backend plays in this and what is handled by Google.
I soon as I've read all of this, who should I go to for questions? @kordianbruck ?

@nerdsupremacist nerdsupremacist self-assigned this Feb 4, 2016
@nerdsupremacist nerdsupremacist added this to the MVP milestone Feb 4, 2016
@kordianbruck
Copy link
Member Author

The TumCabe backend holds the full information on the notification (e.g.: description text for the alarm). GCM is only there to initiate the connection and let the client know that there is new information to fetch. This saves battery power, as we do not have to deal with setup a long lived socket and MQTT ourselfs (Message queue).

Yea, ask me any time - I can give you all infos ;)

@mammuth
Copy link
Member

mammuth commented May 26, 2017

Depends on TUM-Dev/Backend#2

TUM-Dev/Backend/issues/2
backend/issues/2
(Hm, the second both links get changed (the # is added), but it's not mentioned at the backend issue)

@kordianbruck
Copy link
Member Author

The issue referenced above, is already done. It was about migrating to Firebase, which we have completed.
Anyone willing to implement this, please contact me, in order to get the proper certificates for the GCM push messages.

@tgymnich
Copy link
Member

tgymnich commented Feb 22, 2018

@kordianbruck Have you set this up?

@kordianbruck
Copy link
Member Author

yes, I think @mammuth worked on this already and pretty much finish it.

@nerdsupremacist nerdsupremacist modified the milestones: Sometime, 1.3.1 Feb 25, 2018
@nerdsupremacist
Copy link
Member

The preliminary feature needs to be implemented for 1.3.1.
Will only support the Alarm Payload and add chat later.
Updates should be handled differently I guess since the payload appears to be only available for Android and the App Store Updates are pretty fast due to autoupdate

@nerdsupremacist
Copy link
Member

@mammuth can you please push anything you have on this?
@TG908 do you wanna take this one, or should I? I don't know how you're doing on time

@tgymnich
Copy link
Member

Feel free to take this one. I’m still I’m my exam phase.

@mammuth
Copy link
Member

mammuth commented Feb 26, 2018

Same 😞

@mathiasquintero I once checked out firebase and started creating the needed certs and profiles and tinkered around with some code snippets in the app but there is nothing that could be pushed I think.

@AW-tum
Copy link
Collaborator

AW-tum commented Sep 15, 2022

Will be handled in #360

@AW-tum AW-tum closed this as completed Sep 15, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

6 participants