SMS support got more people to use it, its easy to convince friends/family to swap if they can do all their regular texting in there. I understand why they removed it, but I think they did it way too early, they still needed a larger userbase.
@TheEntity@bbbhltz@Lionir To have all communications in a single place/app, and be able to back up / restore in a single place, instead of messing with multiple applications.
If you’re trying to move from using only one messaging platform (SMS) to two (SMS+Signal), then I understand the friction. If you’re like me and you have five other messaging platforms anyway, then a sixth makes no difference. This has never bothered me, but it’s one of the reasons I have not moved my mother onto Signal — it’s added complexity that she’s not really going to understand.
That said, I never enabled SMS in the Signal app and I wouldn’t even if it came back. RCS is available now, and until Android provides third-party app developers the ability to make RCS clients, it’s a dead end.
That makes a lot of sense, thank you for the explanation.
Would you mind summarizing to me the state of RCS on Android right now? You seem to be knowledgeable on the matter and I’m very behind the times on it.
In theory, RCS is something cell phone carriers should support directly, like SMS and MMS. In practice, carriers just didn’t care, so Google built their own RCS relay with blackjack! and hookers!, integrating it into their own Messages app. This works because RCS is designed to run over the internet, and does not strictly need a phone network. Unfortunately, it means you need to use Google’s Messages app.
While Android allows third-party developers to hook into SMS and make their own texting apps, Google has not built RCS support into Android itself — it’s an application-level feature. Currently third-party RCS clients are not possible. I think Google has partnered with Samsung (and maybe others?) to include support in their messaging apps as well, but fans of third-party apps like Textra are out of luck.
I’m not totally sure what the situation is on carriers who directly support RCS. Some of them have simply partnered with Google rather than building their own support. Some of them only support it within their own network (an early-2000s throwback nobody wanted). It’s been a mess and I’m not up on all the latest developments myself.
@GenderNeutralBro@TheEntity one/another issue I have with RCS is that it fails somewhat silently in case of lack of internet access and does not fall back to SMS.
Because if the username is a phone number, it is just very convenient. If someone I know switches then I keep the entire conversation with them and just continue. If I want to encourage someone I know, I can just tell them about the features they’ll get with Signal rather than trying to sell them a platform which kind of sucks on desktop.
Why use Signal for SMS if they are unencrypted either way?
SMS support got more people to use it, its easy to convince friends/family to swap if they can do all their regular texting in there. I understand why they removed it, but I think they did it way too early, they still needed a larger userbase.
@TheEntity @bbbhltz @Lionir To have all communications in a single place/app, and be able to back up / restore in a single place, instead of messing with multiple applications.
If you’re trying to move from using only one messaging platform (SMS) to two (SMS+Signal), then I understand the friction. If you’re like me and you have five other messaging platforms anyway, then a sixth makes no difference. This has never bothered me, but it’s one of the reasons I have not moved my mother onto Signal — it’s added complexity that she’s not really going to understand.
That said, I never enabled SMS in the Signal app and I wouldn’t even if it came back. RCS is available now, and until Android provides third-party app developers the ability to make RCS clients, it’s a dead end.
That makes a lot of sense, thank you for the explanation.
Would you mind summarizing to me the state of RCS on Android right now? You seem to be knowledgeable on the matter and I’m very behind the times on it.
In theory, RCS is something cell phone carriers should support directly, like SMS and MMS. In practice, carriers just didn’t care, so Google built their own RCS relay
with blackjack! and hookers!, integrating it into their own Messages app. This works because RCS is designed to run over the internet, and does not strictly need a phone network. Unfortunately, it means you need to use Google’s Messages app.While Android allows third-party developers to hook into SMS and make their own texting apps, Google has not built RCS support into Android itself — it’s an application-level feature. Currently third-party RCS clients are not possible. I think Google has partnered with Samsung (and maybe others?) to include support in their messaging apps as well, but fans of third-party apps like Textra are out of luck.
I’m not totally sure what the situation is on carriers who directly support RCS. Some of them have simply partnered with Google rather than building their own support. Some of them only support it within their own network (an early-2000s throwback nobody wanted). It’s been a mess and I’m not up on all the latest developments myself.
@GenderNeutralBro @TheEntity one/another issue I have with RCS is that it fails somewhat silently in case of lack of internet access and does not fall back to SMS.
Because if the username is a phone number, it is just very convenient. If someone I know switches then I keep the entire conversation with them and just continue. If I want to encourage someone I know, I can just tell them about the features they’ll get with Signal rather than trying to sell them a platform which kind of sucks on desktop.