Menu
I am looking for pros and cons of Pusher versus PubNub specifically for iOS clients. In terms of resource utilization (battery drain, speed, etc) and delivery reliability. It appears that PubNub has an official iOS library but the Pusher library is created by a third party and not officially maintained? What has your experience been using these libraries?
397
The PubNub iOS client library is maintained by PubNub, and its kept up-to-date to support the latest versions of iOS and XCode. (Just weeks ago, we officially certified our client to work with XCode 5 and iOS7).
PubNub provides an interface to iOS developers which enables them to simultaneously publish to both PubNub native channels, as well as APNS. This makes it possible to send messages to the user's device, even when the device is sleeping or the app is backgrounded.
With PubNub, delivery reliability is provided on both the client and server sides. The server-side caches messages so during temporary network interruptions (driving through a tunnel, transitioning from Cellular to Wifi, 3G->EDGE, etc), upon reconnecting, all messages (missed and new) are available to the client. On the client-side, the client automatically handles connection state -- this way, you are not left to implement reachability APIs on your own to determine whether or not you are connected.
The PubNub multiplexing architecture enables as many subscribed channels as desired to be tunneled through a single connection. Because of this, battery and network resource usage is kept to a minimum.
Presence features are also available which enable all users in a given app to to detect when any PubNub client (iOS, JavaScript, Ruby, etc) is present on a given channel.
If you have any other additional questions, feel free to ping us at [email protected], and we'll get you up and running with PubNub quickly.
Geremy C. - Director of Client Engineering and Support
108
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
