My only regret is that the main alternatives to iMessage are operated by Google and Meta.
Given that the Google Messages app on iOS lacks support for the Rich Communication Services (RCS) protocol, maybe it’s just infinitely difficult to implement. I mean, if it were easy, surely Google would have added it to their Messages app on iOS…Given that the Messages app on iOS lacks support for the Rich Communication Services (RCS) protocol, emoji reactions from Android users will appear as annoying follow-up SMS text messages on the iPhone
I try not to. If I do. There are major boundaries and limitations set.
Don’t know what answer you expect. We can pretend to live in a world where android users don’t exist. But they exist, and they are a fair share of the user base. Also, if you remove your fanboy glasses, there is nothing wrong to use Android. So why is Apple not trying to make the experience better for both kind of users when they use native message services?
While I agree that Google is infamous for shutting down their apps/services, this is not something Google can fix themselves. iMessage is a closed standard and only works with Apple devices, they can't just add support for it.Google needs to explain to iPhone users how RCS is so much better than what we've had the last ten years and why we should support it when Google up and abandoned Hangouts, YouTube Originals, Currents, OnHub, BackupandSync/Drive (still functional, but not anything close to competition), Play Music, Nest Secure, STADIA, FiberTV (I signed up for it, was canceled 3 months after sign up, thanks), Works With Nest API (was great for IFTTT), Trips (Was actually easy to use), Allo, URL shortener, Chromecast Audio (rendered my friend's stereo useless for wireless until he got an iPhone), Google Glass (was supposed to be a revolutionary product, was a dud), Spaces, NEXUS (replaced by somewhat better thought out Pixel), Noop (nope!), Sparrow (couldn't handle competition), Desktop (solved Windows XP's inferiority to Mac OS 10.4), etc.
Google treats new projects like that guy who has a girlfriend for about a year before moving on to the next victim. The first few months are all lovey dovey! "She's amazing, the greatest, other competing phone makers want her! She's a moonshot!"
Then it's "She's great, can't live without her! We're working really hard for a long term thing!"
Then it's This update fixes bugs and improves efficiency - 10/12/2014
Then it's "We have decided to shut down <Insert Moonshot #1,124, 239, 048> due to fluctuating priorities. Final support ends on 09/24/2016. Thank you to all our users who barely made it 2 years with our product/service/"moonshot"! We'll dupe you again in about six months with another "half-moonshot half thought through and half-assed that we will dump into the Pixel 8 Plus Pro Max!"
Most iPhone users think: "iMessage works fine, why does Apple have to fix Google's issue?"
Again, not Google's fault. Apple doesn't allow third party SMS apps. Even if an RCS-only app was technically possible to implement, chances are it would get rejected by App Review.Given that the Google Messages app on iOS lacks support for the Rich Communication Services (RCS) protocol, maybe it’s just infinitely difficult to implement. I mean, if it were easy, surely Google would have added it to their Messages app on iOS…
That would be usefulThis won't work because of Apple's limited tapback "vocabulary". I hope they eventually expand it to all emoji. At least give us an "OK" reaction. I feel like I need that multiple times a day.
Text? Not sent a text / SMS for years.So you never text anyone who owns a non-Apple device?
Except that android will parse the message and show it as an emoji, which means if you are on an iPhone, in a group message with "green bubbles" and another iMessage user "thumbs up" a message, android will see it correctly, but iPhone users get the horrible "spam" from another iMessage user.iMessage already does the exact same thing to an Android user.
When ever an iMessage user likes a message from an android user, it does the exact same thing. Sends a separate text message that the reader like your text.
I don't even know what that is, so nope, not the only one. But from context in this thread, I guess it's some way to respond to a message with an emoji that sticks to the original message? It doesn't seem like an Earth-shattering feature that would cause me to stop sending messages to Android wielding friends...I never use the tapback feature, am I the only one?
Honestly, I would rather them do that. Between Apple bringing iMessage to Android or them adopting RCS into the iPhone, I would much much rather them make iMessage for Android.So you're saying we should give a glass of ice water to the people in hell again?
As a fan of using allegory, this is so well thought 🤣Google needs to explain to iPhone users how RCS is so much better than what we've had the last ten years and why we should support it when Google up and abandoned Hangouts, YouTube Originals, Currents, OnHub, BackupandSync/Drive (still functional, but not anything close to competition), Play Music, Nest Secure, STADIA, FiberTV (I signed up for it, was canceled 3 months after sign up, thanks), Works With Nest API (was great for IFTTT), Trips (Was actually easy to use), Allo, URL shortener, Chromecast Audio (rendered my friend's stereo useless for wireless until he got an iPhone), Google Glass (was supposed to be a revolutionary product, was a dud), Spaces, NEXUS (replaced by somewhat better thought out Pixel), Noop (nope!), Sparrow (couldn't handle competition), Desktop (solved Windows XP's inferiority to Mac OS 10.4), etc.
Google treats new projects like that guy who has a girlfriend for about a year before moving on to the next victim. The first few months are all lovey dovey! "She's amazing, the greatest, other competing phone makers want her! She's a moonshot!"
Then it's "She's great, can't live without her! We're working really hard for a long term thing!"
Then it's This update fixes bugs and improves efficiency - 10/12/2014
Then it's "We have decided to shut down <Insert Moonshot #1,124, 239, 048> due to fluctuating priorities. Final support ends on 09/24/2016. Thank you to all our users who barely made it 2 years with our product/service/"moonshot"! We'll dupe you again in about six months with another "half-moonshot half thought through and half-assed that we will dump into the Pixel 8 Plus Pro Max!"
Most iPhone users think: "iMessage works fine, why does Apple have to fix Google's issue?"
This is kind of the way for me. If I speak with an Android user, it’ll have to be through Telegram, Signal, or in its defect WhatsApp. No SMS.Text? Not sent a text / SMS for years.
Everyone I know uses WhatsApp for messaging. Secure, and cross-platform.
I have to wonder what his definition of "not highly requested" is? 1,000 people asking for it? 1 million? 1% of users, 30%? Plus, how many people know the difference between SMS, MMS, RCS, and even if they did, how many of the people whom want it actually know how to request it? I've seen quite a few people in charge say "Oh, these people don't want/need this," but never really ask them. The CEOs, managers, etc. are so detached from the end users, they don't know, much less appreciate, what the end users need.Apple CEO Tim Cook suggested the feature has not been highly requested by iPhone users.
In group messages, if another iPhone user likes a messages sent by someone, I still get the text saying someone reacted.Thats what I was responding to.
Gotta love a good ‘ol fashion swinging d*** contest. Piss off the users of the other platform so that platform makes a change. I bet apple reacts and implements proper support rather soon. Can we get a poll going?
Noted. I will avoid using the heart Tapback on threads where it will be turned into the horrid heart-eyes emoji.
It’s really useful in group threads. People can respond to a meme or joke with the “haha” Tapback or show their appreciation for something with the heart Tapback without flooding the thread with useless messages.I never use the tapback feature, am I the only one?