Hacker News Reader

Comment by post_break | Hacker News Reader

Hangouts was so close. It had SMS, audio, video, text, desktop clients. It was about to be the android equivalent of imessage. And then they pulled SMS and started pulling other features and pushing duo/allo.

I've switched to telegram at this point and now I have that and SMS. It's a shit show.

View on HN

The bean counters didn't want to pay to be a free SMS gateway.

What Google should do is just build a shared messaging API that can integrate multiple services into one app.

Or they could just do what Apple did with iMessage and just basically use the user's mobile phone as the SMS gateway. SMS I send from my laptop actually get routed to my iPhone and sent to my carrier as a normal SMS using my own plan. This also has the big plus the SMS actually will originate from your mobile number (rather than the SMS gateway's number). Can't see why Google could've gone down this route given Apple has done it with huge success...

> What Google should do is just build a shared messaging API that can integrate multiple services into one app.

You mean something like XMPP? (On which Google's original chat service was based).

No. They should stay out of the backend and do something like a more sophisticated notification API that let's you use whatever service from a unified app. They can slip in their own offering but still support others in parallel.

But they pay for Google Voice?

Reply on news.ycombinator.com