←back to thread

Apple Invites

(www.apple.com)
651 points openchampagne | 5 comments | | HN request time: 1.82s | source
Show context
lordofgibbons ◴[] No.42939855[source]
I really hope this fails.

Apple will use it's dominant position to create lock in like how they did with iMessage instead of cooperating with other platforms on a common standard.

Oder friends and family are surprised when they want to video call over Facetime and find it hard to believe other people's phones don't have Apple apps.

replies(26): >>42939966 #>>42940020 #>>42940243 #>>42940281 #>>42940379 #>>42940471 #>>42940515 #>>42940596 #>>42941069 #>>42941479 #>>42941630 #>>42941758 #>>42942136 #>>42942213 #>>42942456 #>>42942901 #>>42942937 #>>42943397 #>>42943414 #>>42943895 #>>42944072 #>>42944475 #>>42944937 #>>42944944 #>>42947436 #>>42948271 #
canucker2016 ◴[] No.42940281[source]
Blame the telcos for the relative poor quality of text message multimedia (via MMS).

The telcos specify the size limits of MMS messages. iMessage has much higher limits in most cases, so iPhone has to use reduce the quality of the pics/videos to reach the lower size limits for sending to non-iMessage recipients.

For the telcos, why would they upgrade their size limits for MMS - it's just a cost centre for them. They probably make more by selling more iPhones as well.

replies(5): >>42940385 #>>42940390 #>>42940561 #>>42940605 #>>42943359 #
NoPicklez ◴[] No.42940561[source]
I'm an Apple guy and I have to disagree, it's not the Telco's.

Android implemented RCS and Apple dragged their feet in implementing the standardised platform such that high quality messaging was seamless and agnostic between brands

The iPhone needed to reduce the quality of pics/videos to non-iMessage recipients because Apple didn't support any other form of non-iMessage messaging.

replies(3): >>42940594 #>>42941216 #>>42942066 #
Schiendelman ◴[] No.42942066[source]
Have you tried using RCS when you're used to iMessage? It's terrible. Constant failures, weird behavior when changing towers between telcos - not to mention what happens when traveling internationally, where RCS turns on, off, on, off... for a day after arrival.

And of course there's no encryption standard.

replies(2): >>42942199 #>>42943951 #
1. worthless-trash ◴[] No.42943951[source]
I use it every day and across multiple countries in Asia Pacific with no issues.

Maybe its your phone going overseas and not working correctly.

replies(1): >>42946884 #
2. Schiendelman ◴[] No.42946884[source]
On what device?
replies(1): >>42961991 #
3. worthless-trash ◴[] No.42961991[source]
Samsung S22+, Snapdragon 8 Gen 1 (aka everywhere but europe).

I buy an Esim for countries I visit, usually before I go. Add it before the flight, sometimes in the country.

List of countries I have worked with: Singapore (Roaming), Indonesia, Malaysia (I may have been roaming in Malaysia) I can't find the esim info, Thailand, Australia, New Zealand, India (Maybe i was roaming, can't remember).

replies(1): >>42967122 #
4. Schiendelman ◴[] No.42967122{3}[source]
Right. As I said in the other thread attached to GP, Google is actually hacking RCS in a non-standard way to make you work. Apple can't do that, and the RCS standard is basically half done, so it absolutely sucks on any devices that have to use the standard rather than Google's implementation.
replies(1): >>42989254 #
5. worthless-trash ◴[] No.42989254{4}[source]
I assumed you meant google devices. Aka pixel.