Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Twilio's new Notifiy API

techcrunch.com

Post reply on HN
Print view View original

1–10 of 21 posts

Re: Twilio's new Notifiy API

#3

Post by galistoca »

I wonder how this works. Currently there's only a landing page that asks you to request access so I have no idea.

Do developers integrate Twilio SDK into their apps (similar to Fabric, etc.)? If so, sounds like a way different model than what they used to do (Basically you could integrate just by calling their REST endpoint since it was SMS based and required no installation of any app, but with APNS the only way I can see this work is if you tightly integrate with Twilio API by using their SDK)

How do they figure out a number is associated with an account? Does this assume that users will enter their phone numbers when signing up to a service?

Re: Twilio's new Notifiy API

#6

Post by philip1209 »

I need to build a notifications service for our application, and it would be nice if one of my existing tools like Intercom provided the service instead. I want to be able to send messages of varying levels of urgency - e.g. "send password reset now" vs. "this message should arrive within an hour and can be bundled." The service already has communication details - email, phone, push notification info, maybe even facebook auth. I wish it would intelligently route to the correct notification method based on each user's responsiveness (did they open the email?), cost (can I save money by using push vs. sms?) and available methods (e.g. I don't have a twilio number in their country). An API for marking messages as read via a UI notification center would be cool too.

Message spam is the worst, and building intelligent routing across communication methods is becoming a pain.

Re: Twilio's new Notifiy API

#7

Post by pc86 »

TLDR:

> Here is the scenario [Twilio CEO Jeff Lawson] envisions: maybe a user signs up to get SMS from a company (in exchange for a coupon, for example). Then, over time, that user also installs the company’s app on two devices. Now, push notifications allow you to give that user a far better experience, but you don’t want to send both SMS and push notifications to every device the user has the app installed on (that would be annoying, after all). With the new API, you simply set up a rule to send a push notification to the device the user last used (or the one that is currently active) and then fall back on SMS if that doesn’t work.

Post reply on HN