Although for most of the apps rest suffices most of the Messaging apps and real time communication works by maintaining a long lived TCP connection. There are patterns for designing rest api but designing XMPP (or any other long lived TCP connection) is still a mystery. Through this talk I want to bind this gap.
How can we build a chat (or remote command execution) app without consuming much battery and network. In this talk I am going to talk about that. I am going to talk about the wakelocks and other api to design a app with persistent long running service.
Currently working on my startup I have worked on Android extensively previously at Amazon and Kiwi. While working on ecommerce and gaming apps I found the knowledge of rest design (and retrofit) to be sufficient. I learned about xmpp in a hard way while working on my current startup and want to share my learning.
https://docs.google.com/presentation/d/1o25NEXTAIhfFhe_F6pLp-ituIp0YLfOwb0sZ5gxKTg4/edit?usp=sharing
{{ gettext('Login to leave a comment') }}
{{ gettext('Post a comment…') }}{{ errorMsg }}
{{ gettext('No comments posted yet') }}