Google says iMessage is too powerful
arstechnica.com
arstechnica.com
How many messaging systems has Google had over the years?
Their shotgun approach works financially, but it means that only a few of their projects really stick (win). The rest just trundle along until they get discontinued.
The hypocricy is tiresome. When there's a regulation that threatens them, they make a lot of noise about "free market", and "let the market decide". But when the market decides against them, they want some government intervention.
I personally think the current situation with iMessage is garbage. Even if Apple doesn't care about Android users, they are hurting their own users: every time an iPhone user has to send a text to an Android user, they degrade the security and privacy of their own users.
(It's telling to see where Apple draws the line: being anti-competitive around messaging is more important to them than their customers' privacy and security.)
Even if Google had their shit together when it comes to messaging, there's always the "default install" problem: iMessage is on every iPhone, from the factory. That creates a barrier for any competitor to gain market share with an alternative messenger. Sure, WhatsApp, Telegram, etc. have been pretty successful, but they're not the default install. (Remember when Microsoft got in trouble in the 90s for bundling IE, at the expense of Netscape?)
As an Android user, all I really want is a secure way to communicate with others by default, without having to figure out which secure messaging app I have in common with each of my peers. Apple has made that impossible, and should be required to allow Google to integrate iMessage support into the stock Android Messages app. Or they should be required to support RCS (with E2E encryption compatible with Google's extension) on iPhones. I'll accept either option, though I'd probably prefer RCS rather than an Apple-proprietary protocol.
> "Even if Google could magically roll out RCS everywhere, it's a poor standard to build a messaging platform on because it is dependent on a carrier phone bill. It's anti-Internet and can't natively work on webpages, PCs, smartwatches, and tablets, because those things don't have SIM cards. The carriers designed RCS, so RCS puts your carrier bill at the center of your online identity, even when free identification methods like email exist and work on more devices. Google is just promoting carrier lock-in as a solution to Apple lock-in."
There is a publicly-facing Google site to enter an RCS enabled cellphone number, in order to disable Chat features… including end-to-end encryption.[0] This feature should only be configurable on-device, ideally, or at least be behind a login and 2fa. It’s just there on a public site. This is basically asking for sim-swapping attacks. And you’d never notice, only wonder why your RCS e2e keeps turning itself off. I wonder which individuals and agencies may benefit from that…
Even with the Chat features enabled, RCS doesn’t not support e2e on group texts[1], unlike iMessage, which does[2]. Google is just playing dirty pool and calling Apple users bullies by proxy, and I’m calling them on it.
Edit: Apple has a similar site to disable iMessage. This setting should only be available on-device, or if it has to have an online workaround, behind a login with 2fa. If you no longer have access to your phone, you should have to contact Apple support or go to an Apple store. The status quo benefits bad actors and intelligence agencies more than it improves the experience for end users IMO.
[0] https://messages.google.com/disable-chat
[1] https://support.apple.com/en-us/HT202724
[2] https://support.google.com/messages/answer/10262381?hl=en
So for me it seems like a far worse solution than the status quo.
But security is besides the point: Google doesn't want RCS support for security, it wants people not to know they're communicating with a non-apple device because they're afraid of the peer pressure.
Given that android has a huge marketshare lead, and google definitely knows how to make chat apps, they just never made one and stuck with it. Instead they kept continuously shipping new, incompatible, disconnected, chat apps and services. Because of that no one really trusts Google when it says "use this chat app, this time we'll keep it around". Meanwhile a person with a first gen iPhone or iPad (or a Mac from that era) can still use iMessage to talk to someone using the latest generation software. I would guess there's a loss of feature set, but it should theoretically still work.
What you want is for everyone to support whatever messaging protocol Google is pushing today. There have been a lot over the years and it seems like RCS won’t be the last (it has its flaws — serious, fatal ones, IMO).
I don't think that's the way the world is.
I'd prefer the opposite: an OS with _no_ messaging app, and let users pick their own (both for Android and iOS). Expecting OS vendors to ship one out of the box is asking for a new IE-like scenario where whatever big tech companies pick becomes the standard, no matter how good or bad it may be.
Messaging is easily a more competitive market than search.
RCS wouldnt change that one bit.
About 20: https://arstechnica.com/gadgets/2021/08/a-decade-and-a-half-...
Is it still a powerhouse if no one uses it?
I remember my Nexus 5 came with at least two Google messaging apps at the same time.
The problem isn't just churn, it's lack of focus. I wonder how many different teams have been tasked with solving messaging, some at the same time, over the years.
One of the apps they broke off, Allo, literally used phone numbers as IM identifiers but didn't support Google Voice integration and they simultaneously launched a second app, Duo, for video calls instead of just putting it in Allo. How could someone higher up not say "this is the dumbest thing ever, merge the teams or reassign one to something else"???
I was farther in the future of converged communication in 2015 than now.
I'm pretty sure this is taught as a 200-level concept in business administration right?
Only after you manage to recite "short-term profit over long-term success" 500 times in an hour.
In academia, you get kudos for starting something, while there are zero incentives for maintaining something - same at Google with just a tiny bit less hyperbole.
At a large company, you can coast like that playing politics for many years — in Google's case that's especially easy because Ad Words means they have little fear of running out of money and Gmail was big enough to ensure that any new messaging service which integrated with it would immediately “have” millions of users even if many of them had been trained not to use it by that point.
My previous employer was UPS, a top to bottom Microsoft shop, and they were in the process of switching from Skype for Business (Lync) to Microsoft Teams when I left. Even Microsoft has done a better job with their messaging option.
As suggested by this crazy headline, a lot.
“Google to simplify messaging strategy, will support only five messaging apps”
https://arstechnica.com/gadgets/2018/12/google-promises-to-s...
The problem is that open standards just can't compete with closed ones when it comes to giving users what they want (for a nice discussion of this, see the classic https://signal.org/blog/the-ecosystem-is-moving/)
True though that open standards are slower and harder to work with because they involve too many people and too much discussion. Apple is almost exactly the opposite example of this, and clearly their approach works quite well most of the time.
The article answers that:
"Google's messaging history is one of constant product startups and shutdowns. Thanks to a lack of product focus or any kind of top-down mandate from Google's CEO, no division is really "in charge" of messaging. As a consequence, the company has released 13 half-hearted messaging products since iMessage launched in 2011."
I'll hazard a guess that most of those products were left to wither and die due to an inability to significantly advance Google's "eyeballs monetisation" strategy.
However, at some point there are executives deciding strategy, and almost by definition they are out of touch. From my observation, the most reliable strategy is to let a start-up with passion build something great that people want, and then buy that start-up. This is what companies older than Google have been doing for decades. (Google does it too, but they were more in-house-first in the past.)
Apple tends to have user data encrypted in their cloud and to encourage more on-device processing. They are more likely to support data sharing between people via exchanged cryptographic keys than have access within their cloud. Unfortunately, user-initiated sharing delegated access out is not a flow OAuth really supports.
Google's previous social network aspirations caused them to chain access to lots of data through user authorization to APIs. They use API access as one of the attractions to sites supporting "Sign in with Google". AFAIK even API which do not necessarily need any user delegated authorization (such as reading a publicly accessible google doc via API) still require a user authorization.
Apple's APIs typically are not about delegated access to user data, but about access to user's application data (e.g. CloudKit app data access via REST api).
Apple does have a OpenID Connect implementation for Sign In with Apple and have left the option open for it to also be used for OAuth delegated access. So far, there aren't any access token scopes or API publicly documented.
RCS isn't a replacement for Signal or iMessage, not really, but it's a hell of a lot better than the current least-common-denominator, cross-platform approach of SMS/MMS.
Apple, with its desire for vendor lock-in, has every incentive to keep the "least-common-denominator" messaging standard as crappy as possible, to make iMessage's own experience between Apple users more compelling. They have no incentive to improve this and of course will drag their feet as long as possible.
Whatever you think of Google, and whatever you think of Apple, I hope you can agree that the carriers dragging their feet on RCS does nobody any good. There's no reason that RCS cannot co-exist with iMessage on IOS, except that Apple wants you in its walled garden.
Especially being Apple, they would not pick an external pre-standard and run with it when they built their success on in-house design and control. It would also be a huge gamble to build around someone else's young standard.
Do you remember phones in 2011? The Android-based phones were wildly different from each other (often flawed in unique ways). There were still popular Nokia based phones. Apple almost certainly did not target "lock in" as their priority when building their phone software. They targeted "stuff we can control which won't blow up in ways we cannot understand or prevent".
(I do admit their focus shifted after Steve Jobs died, but that was later.)
But also realize the carriers were in heavy competition for decades. I've worked with/for telecom companies off and on for a very long time, and the only coordination really happens when one big company buys another and has to try to integrate things.
Messaging services are sticky and have network effect so there will typically be clear winners - within a particular geographic area or demographic. Other areas/demographics will have other winners.
So perhaps a huge number of American teens use iMessage, while people 30+ use Facebook Messenger. Perhaps a huge number of people in China use WeChat, while Japanese people use Line.
Google is really complaining that very few demographics, not even the masochists, are using Google's chat offerings anymore.
There is no lock-in for the consumer on Google products. If you have a Google device you can use whatever apps you want. If you use Google services you can use whatever apps or OS you want.
The problem is that Google has been too open. They could have made a Google messenging app the default a decade ago and forced all SMS on Android to go through that.
As it stands now, any messenging app can be the default on Android. Some OEMs roll their own, FB Messenger can be turned into default SMS app, etc...
At rough count, around a dozen in ~15 years.
https://www.theverge.com/2021/6/21/22538240/google-chat-allo...
many, but also, Gmail
Similarly, Microsoft would likely be a dominant player in the chat space today if they hadn't rebranded and renamed MSN Messenger several times and then abandoned it altogether.
MSN Messenger was frickin awesome. You could draw pictures into the chat window. You could play a game of checkers while you chatted. It had a thriving ecosystem of apps and plugins. Everyone I knew used MSN Messenger... and then one day, Microsoft just said screw it, everyone can move to slow and clunky Skype... and that was the end of it.
Hell, ICQ might still be around if AOL had put more development resources into it.
The chat space is so bloody fragmented now, but it has nothing to do with Apple. Any one of the above mentioned companies could be killing it in this space if they hadn't pissed away what they had.
Even people like me that hated MS and AOL had chat clients that could communicate with their networks and Google Talk/Hangouts and MSN Messenger were both great for what they were. At the time I felt like we had lost something important by moving to "push" networks versus e-mail but I'd take those days now in a heartbeat. Maybe by 2030, something like Matrix will have us back to what XMPP was doing and I'll be able to send a message to someone's shitty Teams from whatever Google's fifth chat replacement is by then.
It's even worse when I'm traveling in east Asia and there are like 5 different Korean and several Chinese chat networks in addition to WhatsApp trying to be the next LINE and becoming the one-stop access point for nearly everything. I'm honestly expecting to see a 7-11 integrated messaging network at some point.
There were a few brief wonderful years when I had AIM, FB Messenger, GChat, and a few lesser known protocols all in different tabs in the same window.
It's not like they all needed different interfaces; same data, different wire-noise...
Despite living in the US, I actually don't know what's dominant here...is it iMessage? WhatsApp?
Korea is dominated by KakaoTalk. I believe Japan is Line. China I believe has their own walled garden app ecosystems (WeChat & co.?)
Judging from what all my European friends use, WhatsApp dominates at least the UK and Western Europe?
I kind of miss XMPP, which seemed like the answer at one point. As it is, I need about six messaging apps (WhatsApp, Facebook Messenger, Signal, Telegram, a Matrix client, Slack, and I'm probably forgetting one) plus SMS/iMessage to keep in touch with everyone.
WhatsApp seems to dominate in Europe and South America.
LINE and Ali/We chat are now more like platforms, for example, LINE has a wallet called LINE Pay that you can use in retail stores that grew out of selling virtual stickers for their chat client. They integrate to transit services and other things too.
Even still most in Asia also use WhatsApp.
Source: me, I've lived on all continents
Of course I'm talking about the QQ variant, which is probably so far from the original ICQ that I have no leg to stand on making the above claim. Still, a very interesting story to follow.
https://en.wikipedia.org/wiki/Tencent_QQ
Acquired did a fantastic episode on Tencent (owner of QQ/WeChat)
https://www.acquired.fm/episodes/season-3-episode-10-tencent
[1] https://icq.com [2] https://en.wikipedia.org/wiki/ICQ [3] https://en.wikipedia.org/wiki/LiveJournal
Microsoft just kept making it slower, buggier, easier to eavesdrop on, and kept "refreshing" the UI over and over again until it became unbearable.
Same happened with Skype after it was bought by Microsoft, and I seem to recall this is relatively recent. There were (are?) two Skype clients - one for 'personal' (the original Skype) and another for 'enterprise' (rebranded Windows Live for Enterprise possibly?) and not compatible. Again, I recall trying to help confused Windows users figure out why the (incorrect) client wouldn't log-in with certain credentials.
Teams is supposed to completely replace Skype for Business
What are you saying? ICQ is still around.
iMessage is incredibly popular with certain demographics in the United States -- it's an in-group signifier the way teens have always had in-group signifiers (when I was in high school, it was AIM, a Nokia, and wearing Abercrombie) and that isn't about bullying. If Google had its way, its products would be used as the ways to "bully" the out-group. So this is much ado about nothing.
It is notable that iMessage has persisted with its popularity in the US for as long as it has. And it is true that iMessage is definitely an ecosystem carrot, again, in the US. But in countries that didn't adopt SMS/MMS the same way we did in the US (b/c of cost/international variance/etc), the in-group messaging app is something else. It's always fascinating for me to go to other countries and see a ton of iPhone users not using iMessage but something else because that app has become the in-group signifier.
And every teen I know uses Discord more than they use almost anything else. The ranking typically goes Discord, IG, iMessage.
Having said all of that -- even if you took away iMessage, the iPhone would still be a status symbol/in-group signifier for a lot of people, especially young adults in the US. Samsung has had the best track record with some of its devices with approaching similar brand loyalty/"it" factor, but even if Apple adopted RCS -- it's not like the phone all the influencers and cool teens would be using would be Pixels. It would still be the iPhone for a host of reasons that have absolutely nothing to do with technology. White earbuds have been a fashion marker for 20 years now and that's what this comes down to. It isn't about lock-in or regulation or technology. It's about fashion.
Exactly this, Google was happy to be against open communication platforms when it felt it was in their interest but as soon as it goes the other way "Oh we should all be using RCS"
Reap what you sow
I'm honestly surprised more people don't complain about it...and given Google is really the only other big phone software maker now, it is their role to try to say something imo. "You reap what you sow" (as this article says) honestly sounds ignorant (or just pro-Apple) and really ignores the major problem here. Google has been bad at messaging apps, that doesn't mean this concern isn't real or a fairly big problem. Especially when the stats show that this is creating a hardware monopoly for Apple (look at the stats for young people,) in 10-15 years this creates a much bigger hardware market share for Apple. That is not a desirable outcome.
This is supposed to be a technical community so can we stop with this lazy abuse of terminology.
Apple has not hijacked the SMS protocol in any way, shape or form.
They've simply created an app that supports two protocols: SMS and iMessage with a UI that abstracts the difference.
Since this is a technical community, and you're a technical person who presumably knows how iMessage / Apple's infrastructure works, can you explain if this is correct:
- I'm an iPhone user with phone number N. In Apple's system, I'm flagged as supporting the iMessage protocol. Presumably Apple has some gateway that routes messages, and this sends me down the iMessage route.
- I swap phones. I now own an Android device. I have the same phone number N.
- Apple's system is slow to update, and its gateway still sees me as an iPhone user supporting the iMessage protocol.
- All messages from other iPhone users to my phone number are routed incorrectly and I don't receive them until Apple updates its gateway to use SMS for my phone number.
If the above is correct, what would you call that? People who want to contact me have no idea what a protocol is, but Apple has impacted their ability to communicate with me. They think all text messages are the same, but this layer Apple has built isn't open or interoperable, and is additional friction for anyone wanting to switch off their platform.
It's very hard to excuse this behavior.
I think there's a lot of truth to the word "hijacking" here.
On Android you can set Signal as your SMS handler and use it as a similar dual client. I miss that feature when using iOS.
They're a minority phone player. They have their own messaging platform as a feature of their mobile OS, so making it available to other platforms is anathema to their own business goals and success of their own platform.
I don't feel hurt or victimized by their choices here. It's not in my way at all.
That they choose not to support a standard protocol as a competitive advantage is exactly the problem.
Imagine if you bought a 4K television that had AppleTV built in, and then you find out that the 4K feature is only available if you use the built in AppleTV interface, and HDMI is limited to 1080P.
There is a case to be made that such anti-competitive behavior is illegal.
A messaging platform is for communication, not just for the individual customer.
Except stats don't back up what you are saying, at least not in the US. RCS is no less trash than SMS, it's actually an improvement over SMS. They could come together, along with carriers, to create an even better standard but one party is holding out...and blocking any innovation (hint, it's Apple.) I don't get how people are ok with them hijacking an open standard.
Eventually I had to disable iMessage.
Apple iMessage user. The water is fine here.
There needs to be an interoperable, highly functional solution that doesn't depend on wireless carriers.
Apple built a superior service, and the price of using that service is an iPhone. Does it suck for Google and Android users? Yes. Is that the whole point? Yes. Is there anything wrong with that? I don't think so.
I'm an iPhone user, but rarely use iMessage. Most of my instant messaging actually happens on some combination of Google Chat! (or whatever they call it these days), KakaoTalk (I'm Korean) and WhatsApp. Plenty of other alternatives out there too.
I think I have just one friend who I use iMessage with regularly.
It's like a zombie dog that will follow you whatever you do, and will keep eating messages sent to you again and again. There's an ecosystem of tutorials online to go the right step to minimize the effect (e.g. https://www.cnet.com/tech/services-and-software/three-steps-...)
That doesn't look like a "Apple did no wrong" situation from any angle we look at it.
The view that Apple is forced to support other protocols or networks "just because" is pure idealism.
The history of technology and business is a "maze of twisty little passages, all alike" for longer than we admit. Interoperability relies on government/intergovernmental mandating of standards - if you leave it to industry you get patent encumbered formats (see H.265).
Carriers have a lot of control over Android and they simply didn't want to be cut out. Google could have just copied iMessage from the start if it wasn't for carriers not wanting to be cut out of messaging.
You can download WhatsApp or Signal or Facebook Messenger or whatever else you might want, and have those work fine. iMessage works really well, and Apple enjoys some network effects here, but you say "they consider this a competitive advantage" like that's a bad thing.
They made a better mousetrap here. Bully for them!
Signal on Android is a far better experience than Signal on iOS, because the former allows you to choose it as your default SMS app and the latter does not.
In Europe I see people using anything but iMessage, so...
In the US in many places (like teenage users) they do have a dominant market position, and they abuse by actively trying to worsen the user experience of buyers of their products who dare to include an Android phone user in their friend groups.
iMessage took over because iPhone users could no longer send group SMS. Apple killed group SMS. Google never did this. Only tried to change Sms and enhance it.
One of the group chats my wife uses for work is all SMS users except for her.
Or am I misreading your comment?
I've made the switch to Signal, my girlfriend uses it on her iPhone to replace iMessage since I made the switch to Android last month. She can also use it on her Windows laptop unlike iMessage. My family members who are tech-y enough use Signal with me, and when they're not, I can still send standard SMS through the app. Signal even implements responses similar to iMessage 'likes' and 'hearts'. I don't think I could praise Signal enough for the great implementation they've built. Their crypto-enterprise this past year did make me feel a bit slighted, but as I don't use that feature, I can't comment on it.
I'm sure there will be more attempts to come.
- iPhone + iPad? Supported.
- Android Phone + Android Tablet? Supported.
- iPhone + iPhone (no SIM card/no phone number)? Not supported.
- Android Phone + Android Phone (no SIM card)? Not supported.
This, according to them, because they want to simplify the setup experience. But in reality adding a bypass option to the onboarding process to provide the tablet setup experience would be trivial and should have happened three years ago.
You can add this to the "list" like no Gifs on PC even though the code exists for mobile clients, and they share a lot of source code already.
To do so, you have to go into your default apps, set the default messaging app to Signal (factory default is Messages for Pixel devices, likely whatever Samsung uses for Samsung devices). I just checked to see if there were any extra settings you have to enable in the Signal app, but it doesn't appear to be so. If a user uses both SMS or encrypted chat, you can long press the send button and decide between which it will use.
Do note, that any previous messages sent via SMS from other apps won't show up in Signal for message history. Likewise the same if/when you switch to another SMS app.
Google never seemed to understand this convenience. They released Allo without any SMS support and were hostile so suggestions that it was a gating feature to adoption. Allo predictably failed as it offered no benefits over competing services, and no SMS fallback so that it could be the single messaging app.
If Google wants to level the playing field they should do it by competing and innovating. I suggest they start that endeavor by better understanding why people actually use iMessage in the first place.
Hangouts on a Google Fi phone used to let you consolidate everything to hangouts - SMS, Chats, Calls, etc. It was a pain it was limited to Fi, but it worked just fine. You could also pop open Hangouts in Gmail in your browser and there all your sms messages were, nicely grouped and tracked.
Then apparently hangouts stopped being cool enough - so Google decided to shutter it in favor of "Google Messages". Technically - "Messages for web" also supports the same feature set as the integrated hangouts, but it FUCKING SUCKS.
The phone/browser syncing is bad, the UI is a complete regression. Just the process of enabling it required me to actually contact support at google fi (you have to open settings, disable previous sms settings for fi, stop hangouts, update your google account, and then opt into a beta).
Basically - Hangouts did exactly this, but Google continues to act like Google, and shutter any product that might actually be a good foundation to build/maintain, since Google has shown AGAIN AND AGAIN that it can't actually maintain any product.
Google can innovate just fine - it's the follow through that they lack.
Google has messengers on every android phone preinstalled and nobody uses them, because they create them, never significantly update them and then abandon them. It's completely their fault they don't even get a mention when people talk about messaging apps.
Around the time that they started f-ing around with 15 different chat apps and killing off products, and integrations with other products, was when a Google account with "integration" started to become more of a hassle than worthwhile to me, personally. I used to use gChat, Hangouts, etc. but now I just use iPhone stuff since everyone I know has iPhone stuff. Apple hasn't deprecated anything since at least 5 years ago (the last time I had a work iPhone) so to me that signals that I can keep iPhones and not have to continually figure out what the "new way to chat" is, like I had to with Google. I've almost completely migrated from Google, except for Photos (which is superior to alternatives, IMO; I can actually backup my Google Photos from my Linux CLI whereas I couldn't figure out how to reliably do that with Apple Photos) and Google Search usage. I have had my Gmail account since ~2004 and I basically killed/deleted all of the services in my Google account now (even Google Voice sucks now, so I basically abandoned my phone number I used from ~2001 that I ported into it) except for forwarding email to my new email address and using Photos. I used to be "all in" with Google, but they made it too hard to keep using stuff that kept being killed off, so they dug their own grave.
I've since switched from Android to iOS, but Fi+Hangouts was amazing at the time. Too bad Google seemingly abandoned both projects.
Of course Google has killed all that many times over. They made their own bed.
I never understood why Google didn't just clone Apple's app many years ago. Hangouts was pretty close - take that, add e2e encryption for in-app threads (like iMessage) and make sure SMS is there as a peer. Make a client for the major platforms and then let the project slip into maintenance mode.
Instead, they championed RCS which (last time I checked) isn't encrypted which is borderline unethical IMHO.
Network effects are big and they were intentionally reducing theirs! Shockingly it hasn't gone well since then.
We've never really dug in to why, as we're both using the default app. No other conversation has ever had this blue message and lock symbol and checkmarks going on.
Given iMessage basically has no base outside of the US because everyone uses Whatsapp or Line I'm not convinced this is terribly neccessary.
HN opinion has been negative on Google for a while, and this is filtering into the consumer landscape.
It doesn't mean they are going out of business tomorrow or at all, but I see a period of MSFT-like regression, reflection and then a Nadella to bring them out of their malaise.
On the other hand, the US is unique for this because iMessage is not as popular outside the US.
I've always seen it this way:
Facebook is trying to be the new Google.
Google is trying to be the new Microsoft.
Microsoft is trying to be the new IBM.
IBM is trying to be the new Oracle.
Meanwhile, Apple is trying to be the new Sony.
At this point, Sony wishes it could be Apple.
There is a publicly-facing Google site to enter an RCS enabled cellphone number, in order to disable Chat features… including end-to-end encryption.[0] This feature should only be configurable on-device, ideally, or at least be behind a login and 2fa. It’s just there on a public site. This is basically asking for sim-swapping attacks. And you’d never notice, only wonder why your RCS e2e keeps turning itself off. I wonder which individuals and agencies may benefit from that…
Even with the Chat features enabled, RCS doesn’t not support e2e on group texts[1], unlike iMessage, which does[2]. Google is just playing dirty pool and calling Apple users bullies by proxy, and I’m calling them on it.
Edit: Apple has a similar site to disable iMessage. This setting should only be available on-device, or if it has to have an online workaround, behind a login with 2fa. If you no longer have access to your phone, you should have to contact Apple support or go to an Apple store. The status quo benefits bad actors and intelligence agencies more than it improves the experience for end users IMO.
[0] https://messages.google.com/disable-chat
[1] https://support.apple.com/en-us/HT202724
[2] https://support.google.com/messages/answer/10262381?hl=en
iMessage is really good because Apple focused on making a great product.
Google just deployed the same logic to remove dislike counts on YouTube, despite those being valuable for users.
The article is not quite correct. The base RCS standard does not include E2E encryption, but at least Google's implementation includes it as an extension. Not an ideal situation -- IMO it should be a required-to-implement part of the base -- but it's definitely there for those of us using Google's infra, at least.
Part of the elegance of iMessage is that E2EE isn't optional.
Kids without phones may even, gasp, be bullied over it. Wouldn't that mean that Google, Apple and all handset vendors benefit from fear of bullying over not having a phone at all?
https://www.theverge.com/2021/6/21/22538240/google-chat-allo...
[1] https://en.wikipedia.org/wiki/List_of_Google_products#Discon...
Besides, almost everyone uses Whatsapp, regardless of the phone brand.
In fact, here is a small taste only with French data, which I guess is still an European country.
https://www.statista.com/statistics/1188330/sms-traffic-volu...
For me and my peers, SMS is for 2 factor auth, spammy advertising, and the occasional parent that mistakenly sends a SMS instead of a WhatsApp message.
If they had just kept iterating on Google Talk and made it similar in functionality to iMessage, they would be in such better shape today. Instead, they’ve thrown away the last ten years on messaging.
Would do regular SMS messages but you could configure your AOL, MSN, and even Facebook messaging at one point IIRC all inside of the same interface. It's too bad it lost out compared to Android. Was so far ahead in so many areas.
Hangouts was cool much before iMessage and Zoom as mentioned in the article. I remember it being my main messaging platform. I remember being amazed with the video chat quality with multiple people. Google was at least 5-6 years ahead of the game. But then, it just fell more and more behind.
As far as Google products go, nothing is user-centric and everything gets clunkier. Only Google product that feels staying alive is Google maps and maybe Google search. Not that Bing is better but there are times, I Bing a search to find something I can't find in Google search. I feel like even Gmail is falling behind now; it stayed the same billion years. Simple filtering, organizing tools stayed the same.
https://www.washingtonpost.com/technology/2020/10/19/google-...
https://twitter.com/mwseibel/status/1477701120319361026 (posted on HN)
Hilariously, I had to use bing and HN's algolia search to find these
https://cdn.arstechnica.net/wp-content/uploads/2022/01/scree...
Convert that screenshot to grayscale in Photoshop to see
https://i.imgur.com/U8mEB93.png
This has always bothered me. Apple definitely knows this and is doing it on purpose. The color green they chose is just hard on the eyes. They don't think it's a good color.
On mine, that screenshot looks like the green has an unpleasantly high saturation compared to the blue. The higher saturation increases the perceived value/lightness, lowering contrast.
[0] On my phone (a Pixel5a running Android 12), Display > Colors is set to Adaptive, rather than Natural or Boosted.
This bit annoyed me; while the base RCS spec does not include E2E encryption, Google implements it as an extension. Now, I don't know how their implementation works (is it the Signal protocol? is it some homegrown thing? haven't looked into this), and it absolutely should be in the base RCS spec as something that's required to implement, but saying it lacks E2E encryption is not quite correct.
I think he's right: the big problem I have with SMS is that it's run by the carriers, who are terrible at non-phone infrastructure — that's how you get SMS delivery latency ranging from seconds to days, completely opaque to the user, and new features are a long, slow grind. RCS preserves that model going forward.
iMessage benefited tremendously from being the default. Combine that with Apple's mobile market share in the US and you get the present situation.
My gripe isn't really that it won in the US. Its that you need Apple hardware to participate.
Google may be self interested but they're right about one thing: knowingly allowing and fueling this social dynamic is inconsistent with Apple's brand. But it was never really about values, just making consumers feel good about their purchases.
Can WhatsApp do sms/mms now?
Now, what is the selling point of a Pixel phone? They are designed to spy on and abuse their users by default. The entire business model is built around collecting data on you for sale to other parties. Phones are VERY personal, most people wouldn't even share their phone with a friend!
Maybe phones have just become too personal as a device? Maybe it is time to close the book on businesses like Google that ship shiny spyware where the utility features of a phone (messaging) is an afterthought...
Been doing this for about two years and now ~80% of my personal conversations are over Signal. And most of these friends are not very technical.
I love my little successful rebellion against the walled garden. And it will make my eventual transition away from iOS much easier.
Just a somewhat related personal anecdote, sorry to deviate a bit from topic.
EDIT: Yes, Signal is centralized and I would have loved to use Matrix. But the clients are bad. Email me if you want to build a better one
I travel a lot and now essentially live in 2 different countries at once so tying all my communication to a phone number is a no-go. Now FB messenger ironically is my go-to (only real cross-platform app that everyone seems to have), even though I'm not a fan of FB at all.
I remember when iMessage came out, and for some people it was a way to get away from getting charged for texts. Especially international! Things have changed so much it's hard to see the original inspiration in 200x.
As for interop, in 2020s it looks like platforms are the style du jour, things like XMPP didn't quite cut it. I'd be happy to see that change, but for google to lay this claim sounds lazy to me.
"If the company really wants to do something about iMessage, it should try competing with it."
Bikeshedding at scale. This is what it looks like. I'm surprised that their home automation systems don't have some incompatible chat platform embedded in them.
If you're a Google Fi users (cell phone service) you have to do some wonky hacks to make iMessage work because Google doesn't support it. Then every time you run a software update, you have to re-enable iMessage.
Google lost a fight, and is crying about it.
They do EVERYTHING in their power to screw over people on iPhones... and then they want Apple to play fair? Ha.
The worst thing is that when you travel between countries, iMessage is really the only good way to text friends without getting silly international text fees.
Therefore, all of my friends have to have iPhones... or I've basically stopped texting them. It's sad. But hey, that's on the phone companies too for charging money for texts. It's all shitty.
But Google being shitty and then bitching about Apple... that's rich.
Or, in less loaded and hyperbolic terms, a visual indicator of the medium used for the conversation.
Jony and Apple could have left a switch setting for black letters instead, but no, the Apple way is read white letters on a mid-tone gradient.
My last iPhone, I never upgraded it from iOS 6 because I didn't agree with this design direction, and I have to say it's a breath of fresh air using Android because you don't have to deal with a single guy making all the decisions for you.
RCS would be a regression for people who /do/ use iMessage, as RCS can randomly drop encryption, does not support multiple devices per account, and does not support group messaging. In addition to that, RCS's feature set is defined by carrier groups, who like to charge extra for "value add"/new features, and who don't move at the speed of tech release schedules.
At its base level it is meant to be e2e encrypted but that fails frequently enough that google has to have special UI to indicate the failure, even though they endeavor to minimize how visible that indication is.
For group chats (the ones that seem to pop up in examples) RCS does nothing: it isn’t e2e.
Group e2e is challenging, which is why it’s still rare even though it has been the behaviour of messages’ group chats since day 1. That said it is mind blowing to me that the carriers specified RCS’s group protocols as anything other than fully e2e. If you’re going to make it a standard you don’t get to half ass it. :-/
Then as others have said, in RCS your keys and account are tied to your phone number. This is not as much of a problem in the US, but in many countries changing carrier means changing number.
This can't be true, because if it is there is bigger problem than some google's protocol. Why are they still torturing kids with these parades? Get some celebrities to make the green texts cool, this is madness.
"Server for forwarding iMessages to clients within the BlueBubbles App ecosystem"
You have to have a mac desktop/laptop/VM to use it. Pretty complex setup process, but looks promising.
For a company that is reticent about so many important problems, this seems like poor form.
For the rest of the world, I don't think it'll ever pick up at all. SMS is long dead in the past, and, AFAIK, only still relevant in the US. Elsewhere, SMS is for verification codes and spam.
The only bad part here is that YouTube's days are numbered. The other stuff doesn't matter. I suspect that worldwide iMessage and whatever Google is pushing on a given day is a rounding error.
They are using hype to increase their stock and axe them later to show a better earnings report further increasing stock prices.
They are intelligent and runs on innovative hype but at their heart they’re an advertising company.
[0]https://www.theverge.com/2021/9/7/22660516/tiktok-average-wa...
SMS is like a spam graveyard where 2FA codes and other regulatory compliance related stuff shows up. SMS is primarily texts from my bank and spammers. Most folks in the rest of the world are using WhatsApp, with the occasional country where Telegram is more popualr.
Messaging with a layer of rich features for billions seems like a hard problem. I'm not sure what iMessage is built on, but WhatsApp is using customized erlang/ejabberd and Telegram is its own golang MTProto stack. Each probably handle millions of connections on FreeBSD or something I suspect.
Is it still a powerhouse if no one uses it?
These threads are hilarious for anyone that's not part of the chosen 3% (or whatever) of the worlds population.
That's not what RCS is.
Can you use it not on the smartphone?
Can you use it without cellular data Eg with Wi-Fi only?
Can you throw out the SIM card and still send/receive messages?
If the answers is 'no' then it is a carrier lock-in.
Identity seems to be tied to a number (not carrier), but Messages uses Google Contacts as an optional layer of indirection.
So, if you change your number, and the other person changes (or adds) the number to your existing contact, your identity is preserved (for them). If the other person creates a new contact for your new number (or doesn't associate the new number with any contact), identity is not preserved.
> Can you use it not on the smartphone?
Yes, you can use Google Messages for Web on a computer, but the authentication is still tied to the phone via a QR code, and I think that communication actually is relayed through the phone if the conversation is via SMS rather than RCS.
> Can you use it without cellular data Eg with Wi-Fi only?
Yes.
> Can you throw out the SIM card and still send/receive messages?
I think that the answer is generally 'no', but there are a few edge cases (eg. I'm not sure what happens if you auth Google Messages for Web on a computer, set it to remember the device auth indefinitely, and then remove the SIM or turn off the phone).
> If the answers is 'no' then it is a carrier lock-in.
As you can see, the answer isn't quite so black and white.
RCS works through QR code outside, just like you can end text-messages.
Why throw out a sim card? You can use RCS with ANY carrier. If you can use it with ANY carrier, it's not carrier-lock in.
In Belgium, the number is personal and not from someone else. If you transfer carrier, you are allowed by law to take the number with you.
In those countries where Apple didn't have a > 50% market share in the early '10s, people simply couldn't use iMessage. For instance, this is a summary of how things went in Italy. I think something along these line could have happened in most other countries where prepaid traffic was the norm though:
1. In Italy, basically the entirety of mobile plans were and still are prepaid, which meant you charged your account with money which you then used to pay for your traffic. Most people also had plans you could easily change, which gave you stuff such as SMS and phone calls minutes for a fixed fee, and you paid for them using prepaid credit. More "serious" contracts were heavily taxed, and thus only make sense for corporate phones or if you have a VAT account to deduct some of the taxes (and even them they were not the cheapest option).
2. No prepaid plan included unlimited SMS until around 2015, when they had already become largely irrelevant to most people. Before then, you generally got a very limited amount of SMS per month or day, and those were often tied to numbers belonging to the same carrier.
This meant that most people in a certain area were basically forced to stick with a certain MVO for most of the '00s. For instance, a very popular 2007 Vodafone prepaid plan in Italy costed €6 per month, and included 100 SMS a day towards all Vodafone numbers (99 actually, you had to pay the first one). Having the "wrong" carrier in that time period meant that people had to pay a lot of extra credit to have a proper conversation with you - this was often a deal breaker for romantic relationships among teenagers, or led to people not contacting you at all. A very interesting time indeed.
3. MMS were basically never included in any plan ever, and when they did, they had the same limitations as SMS. Often, if your plan followed the "pay the first message, get 99 free" clause this was also true for MMS, meaning you had to pay for the first SMS AND the first MMS. If People were so wary of them that they actually deleted the MMS APN from their phones to avoid sending one of them by mistake - if you wanted to send a photo to someone you simply waited until you got home, in order to use MSN Messenger or email. The only usage of MMS I remember of in the '00s was sexting.
3. When iPhones and Android came out in the late '00s, data packs suddenly became a necessity to most early adopters. The iPhone heavily pushed its Internet capabilities a lot, and you often had just spent a hefty sum (remember: prepaid meant you had to pay the whole phone cost upfront) so you wanted to squeeze value out of it. Carriers at the time came out with the idea of selling extra prepaid packs with a limited amount of data (i.e. 50 MB a day, or 500 MB a month), which was not an awful lot but it was enough for maps and some light browsing.
4. I actually bought an iPhone 3G back in 2008, and it was truly amazing for its time. I paid around €550 for it, which was quite a lot for a teenager - I had to sink a lot of the money I had earned from my summer job in order to buy that. Most people around me were very against the idea of spending so much money on a phone - after all they could get by by simply buying a random Nokia 6610i or whatever for €100 and pay your 10 euros a month in prepaid credit and do whatever you needed to do. The fact that carriers in countries like the USA basically forced you into 2 year plans meant that you often got iPhones for cheap, which helped get a foothold in the market.
5. When people started to actually switch to smartphones around ~2011, most people picked up shitty €200 Android phones which utterly sucked, and the higher end saw a lot of fierce competition between the iPhone, Samsung Galaxy and the likes. Still, you could expect at most 1/5 of your contacts to have an iPhone, and still people were locked in those carrier walled gardens when sending SMS. If they had an iPhone you could send them iMessages, but that was not the case. The fact iMessage was integrated in the SMS app didn't help either: people back then had to actually _count_ how many SMS they had sent a day to stay under their daily caps, and mixing in special messages you didn't have to pay was actually pretty confusing. I think most people in Italy today still don't really know what iMessage is actually.
6. Data is carrier agnostic - as soon as true chat apps with push notifications such as WhatsApp and FB Messenger came out, people started using them as a loophole to avoid paying for MMS and SMS. Group chats, which were really not feasible before (remember: SMS caps), suddenly became popular. Feeling left out, most people left feature phones in order to use chat apps, causing SMS to quickly disappear in less than a year. As an example, I went from sending 100 SMS a day in 2012 to 20 a YEAR in 2013.
Good point. Messaging apps enabled group chats for real this time. SMS was something like proto/quasi messaging app.
>I live in Italy and I haven't received a single SMS from an actual human being in several years.
Btw spammers still use SMS. But spamming bots are not humans tho ;)
I suspect Apple will eventually support RCS as a strong improvement over SMS. This will help a lot with bridging the gap, but Apple will still use iMessage as a differentiator.
"Teens and college students said they dread the ostracism that comes with a green text. The social pressure is palpable, with some reporting being ostracized or singled out after switching away from iPhones."
Why is text color an issue? Or, is it just a stand in for referring to the different apps?
In a one-on-one conversation, it’s not the biggest deal…but in a group text it is a massive loss of functionality, enough to make people set up separate group texts with only iPhone users to restore the lost functionality when they don’t need to message the non-iPhone users.
It makes it very difficult to exit the Google system when I tried to migrate to Fastmail.
I don't really trust Google to manage messaging long term. Their messaging products have changed so often, I gave up trying to use them.
From there, you just need to export the data you want from the messages db. The schema is kind of amazing, but not in a good way.
You don't need to buy a tool - you can write a python/ruby/whatever script.
The article promotes a zero sum mentality. That only apple should win because iMessage is better and because google already messed up.
As opposed to a value oriented mentality that a new standard, RCS, could be better for android and iOS users alike.
Google hasn’t always been a great company. I don’t understand why we can’t celebrate wins, especially those that would benefit others, such as rcs.
To do otherwise is to indefinitely call some parties good and some parties bad, to engage in black and white thinking. Which is more harmful for ourselves and says more about ourselves than the individuals and corporations of the world.
It's rightfully calling out Google for calling out Apple when both companies are to blame for this.
The author clearly doesn't like RCS, which is an opinion he's entitled to.. but Google's approach to try and get multiple vendors to adopt an open standard (RCS), instead of creating a walled garden seems like the better path.
Google sounds like dudes who whine about cancellation.