Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Switching from iphone, which all my friends and family use, to a pixel caused so many issues with texting I almost went back to iOS solely because I was causing headaches for others.

FOMO is real for sure, but plain old inconvenience is also at play. If your entire family and social circle is on iOS, it's a massive pain to leave. This is by design.



I completely understand what you mean by this, and what bothers me the most is that this is problem should be entirely avoidable. Pleaes correct me if I'm wrong, but I can't think of a single technical reason why "a non iphone in a group chat" has to cause such infuriating levels of inconvenience for everyone involved. Someone had to put explicit effort into making it as unbearable as it is.

The only reason I can think of is Apple using a dominant position in a network in order to sabotage alternatives.


> Pleaes correct me if I'm wrong, but I can't think of a single technical reason why "a non iphone in a group chat" has to cause such infuriating levels of inconvenience for everyone involved.

SMS/MMS is the lowest common denominator for non-Messages devices. So including a non-Messages device in a group chat means the whole chat needs to be downgraded to SMS. Even if Apple added support for RCS tomorrow, group chats would need to downgrade to it and lose E2EE and rely on the participants carriers to deliver messages just like with SMS.

There's no good way for Apple to integrate the shit show of non-Messages protocols in a sane way. Carriers made a mess of RCS in the design, implementation, and deployment. Google has had to run their own RCS backend to allow Android users to actually use RCS thanks to the carriers' bungling and meddling. Even they haven't helped the situation with a decade of half-starts in messaging apps.

Blaming Apple is a bit ridiculous. They're not going to spend a billion dollars fixing the problems created by carriers and Google when they already have their own messaging system.


It's a problem APPLE CREATED! this is texting, plain and simple. Apple decided to do their own thing and call it texting instead of just making their own entire messaging system. Now people are brainwashed... But only in the US really...


> Apple decided to do their own thing and call it texting instead of just making their own entire messaging system.

They did make their own messaging system. Their Messages (née iMessage) is entirely separate from carrier provided SMS/MMS. It's accessed via the same application as SMS because on early iOS they only supported SMS. The Messages/iMessage features were added to their existing application.

Saying "this is texting plain and simple" ignores a ludicrous amount of complexity about the underlying systems. There's nothing plain and simple about text messaging systems. If you're going to bash Apple for supposedly creating problems at least familiarize yourself with the subject.


Google also attempted to do this with Hangouts by making it the default SMS client. With a bit of follow-through, it might have been successful.


>Blaming Apple is a bit ridiculous. They're not going to spend a billion dollars fixing the problems created by carriers and Google when they already have their own messaging system.

I blame Apple for making communications software (iMessage, FaceTime) that is utterly useless to me as an Apple customer.

There are exactly two useful ways to make this kind of software.

(a) Build on top of a standard that others can implement for other platforms.

(b) Support all big platforms yourself.

Apple has decided to do neither. They made something that is totally useless for everyone outside of some close-knit circles in the U.S. Lock-in strategies are always lock-out strategies as well.

But they're not just pissing off their own customers, they're also playing a very risky game. Messaging apps have a tendency to become platforms in their own right (e.g WeChat).

By taking itself out of the picture, Apple is creating a power vacuum that is being exploited by the likes of Facebook. Ultimately this could even threaten Apple's hardware sales, for instance if Facebook manages create something interesting out of WhatsApp + Oculus.

So in my opinion, Apple's strategy is unintelligent and norrow minded. It's classic short sighted "corporate greed".


When Apple released iMessage and FaceTime respectively there weren't really good "standards" for them to adopt.

For iMessage there were desktop messaging standards like XMPP or the immature at the time RCS from cellular carriers. XMPP is not a great protocol for mobile devices with unreliable/changing network connections and background processing constraints. RCS was immature when iMessage was released and hadn't really been deployed by carriers or was deployed but not interoperable between them. It also requires a SIM and a cellular service. So it's a non-starter for non-phone devices. Additionally it doesn't offer E2EE without proprietary extensions and running private relays like Google has done.

For FaceTime there was never a really good video telephony standard to implement. FaceTime uses some existing standards but all over Apple infrastructure. Remember FaceTime has always been an over the top data service and like iMessage has no tie to carriers. When FaceTime was released it didn't even work over cellular, it was WiFi only.

So what standards should Apple have adopted? As a minority player in the mobile or computer markets which of their own services should they have pushed as standards?

Obviously standards are the way to go since WhatsApp, Signal, Telegram, WeChat, Facebook Messenger, Skype, and Google's 400 different messaging systems all implement the same standar...oh wait they don't.

Messages is a value-add for Apple's platforms. Google isn't bending over backwards making Nest devices work with Apple ecosystems and Microsoft doesn't offer an XBox SDK for the PlayStation. WhatsApp isn't opening their messaging for Apple to adopt. Companies compete with one another, making products and offering services to attract customers. Why is this unintelligent and narrow minded when it's Apple?


>So what standards should Apple have adopted?

If there was no suitable standard then they should have created one. Either that, or support all major platforms.

>Companies compete with one another, making products and offering services to attract customers. Why is this unintelligent and narrow minded when it's Apple?

Because it's classic short-termism for the narrowest financial reasons, showing no creativity or vision whatsoever. They prioritised locking in some U.S based users at the cost of creating an oppportunity for the likes of Facebook to serve the overwhelming majority of users for whom Apple's offering is useless.

I have no problem in principle with proprietary software that is only available on a single platform. What I find unintelligent and even offensive as a customer is choosing this approach to create this specific type of software that so obviously requires a different approach.

For me, iMessage and FaceTime do not add value. It's preinstalled crapware that causes massive security issues.


They created their own messaging system and let SMSes enter it. You can't send an SMS to a WhatsApp group. Problem solved.

Of course you can install WhatsApp on any phone but you can't install iMessage on Android so maybe Apple had to let SMSes in.


> They created their own messaging system and let SMSes enter it.

Apple supported SMS before iMessage/Messages existed. Their Messages app didn't even support MMS until iOS 3. It didn't gain the iMessage functionality until iOS 5.

Apple supports the global standards of SMS/MMS. Their own Messages service can be disabled entirely so a phone will only send SMS/MMS messages. Just about any phone able to connect to an extant cellular network can receive these messages and send messages to an iPhone.

SMS and MMS lack a lot of capability that people want in messaging systems. SMS was born out of unused space in control messages in the GSM spec. That's why fucking everyone from DoCoMo (i-mode e-mail) to RIM (Blackberry Messenger) to Apple have added some over the top messaging system to phones.

SMS is a fallback because it's supported by essentially every carrier. Carriers have tiptoed towards a better messaging standard with RCS but they are at cross purposes with OS vendors and end users. They want a messaging system that allows them to charge per use and the ability to snoop on user messages. So they turned RCS into a mess of a standard and have bungled or slow walked it's rollout.

But no, I'm sure it's Apple that caused all the evil in the world.


A trillion dollar company should be able to easily figure out how to avoid "reaction" messages from dumping a screenful of text and destroying the messaging experience for everyone. I"m sure they can do it for less than "a billion dollars".

I'm not suggesting that Apple should be responsible for making cross-platform messaging 100% compatible, but someone at Apple has made conscious decisions to make the experience as infuriating as possible.


RCS is great. They should have done it ten years ago.

Sure, ten years ago it probably didn’t seem to matter, but the iPhone 5 already bumped the screen size from 3.5in to 4in the rear camera was already 1080p, and “phablets” were already a term in 2012. It was totally foreseeable that MMS size limits where going to be a problem, if they weren’t already!

What a great case of skating where the puck is, instead of skating where it’s headed. RCS existed as a spec, just not implemented by carriers. The fact that Apple, and even Google, are routing around their MMS servers is totally their fault.


And if everybody is on WhatsApp or Messenger or Telegram nobody really knows of you have an iPhone unless they look at you carefully when you use your phone. It becomes a commodity if we care only about messaging.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: