My company is developing a real-time interaction android application that requires web socket to push and pull the messages seamlessly. During the tech team kick off, we have few choices in our minds such as parse, firebase and socket io, and we ended up with socket io for high flexibility, low cost and full customization.
While we are going deeper into development, I am pretty impressive with the power of socket io. Socket io requires a socket to be opened in the background service, so that users can receive the notifications even the application is not opened.
Unfortunately, some phones will automatically kill the background service when user exit the application, unless user explicitly grants the permission in the setting. If the background service is killed, no update will be received.
This is the thing that I have been worried about. Does firebase have any magic to allow real time notification with no background service created by the app? I guess firebase and socket io are using same technology i.e. web socket to communicate, but since Android is developed by Google, they might have some unknown magic behind the firebase.
via Fernando Tan
No comments:
Post a Comment