96 ms·
It seems fairly limited right now, and doesn't do much to alleviate the pain of supporting many different push notification services. You still have to code th
by Rezo 13y ago
It seems fairly limited right now, and doesn't do much to alleviate the pain of supporting many different push notification services.
You still have to code the client side pieces for each platform separately instead of providing a uniform SDK, you then communicate the notification URIs "somehow" to your own backend and store them on your own. The only difference seems to be that you would then talk to Amazon's API instead of directly to for example Google Cloud Messaging from your backend. I'm not sure it's worth introducing an abstraction layer just for this slim piece. Hopefully they'll broaden scope later on.
WNS & MPNS support for Windows 8 / WP8 notifications also appears to be missing.
- barake 13y agoFor what it's worth, the new Azure Notification Hubs[1] present a fairly uniform API across devices. [1] http://www.windowsazure.com/en-us/documentation/services/notification-hubs/ http://www.windowsazure.com/en-us/documentation/services/not...
- zwily 13y agoThis is just abstracting the process of sending a notification to the different backends - which is fairly significant. Apple, for one, requires you to hold open a TCP connection to them, they don't provide a REST-ish sort of interface for sending notifications. The client-side piece is still a bit messy, but that's not where AWS plays anyway.