Android
DROID DOES
Welcome to the droidymcdroidface-iest, Lemmyest (Lemmiest), test, bestest, phoniest, pluckiest, snarkiest, and spiciest Android community on Lemmy (Do not respond)! Here you can participate in amazing discussions and events relating to all things Android.
The rules for posting and commenting, besides the rules defined here for lemmy.world, are as follows:
Rules
1. All posts must be relevant to Android devices/operating system.
2. Posts cannot be illegal or NSFW material.
3. No spam, self promotion, or upvote farming. Sources engaging in these behavior will be added to the Blacklist.
4. Non-whitelisted bots will be banned.
5. Engage respectfully: Harassment, flamebaiting, bad faith engagement, or agenda posting will result in your posts being removed. Excessive violations will result in temporary or permanent ban, depending on severity.
6. Memes are not allowed to be posts, but are allowed in the comments.
7. Posts from clickbait sources are heavily discouraged. Please de-clickbait titles if it needs to be submitted.
8. Submission statements of any length composed of your own thoughts inside the post text field are mandatory for any microblog posts, and are optional but recommended for article/image/video posts.
Community Resources:
We are Android girls*,
In our Lemmy.world.
The back is plastic,
It's fantastic.
*Well, not just girls: people of all gender identities are welcomed here.
Our Partner Communities:
view the rest of the comments
Every now and then, I consider using a Google product, and then I remember this.
RCS is not a Google product but the official SMS successor.
Yes, but I'm pretty sure that Google users their own proprietary model and their own servers. So they took RCS and built on it. Not to mention that Google Messages is a Google product...till they kill it or rebrand it, like they did with Google Allo. From Google's FAQ page on RCS (everything mentions "Google's backend"):
How RCS chats work? When you use RCS chats by Google, messages are sent and received through Google’s RCS backend over the internet. Messages can either be delivered to or received from users on other RCS service providers. If RCS chats are provided by Google, but your recipient’s RCS service is with another provider, your messages are routed through Google’s RCS backend and then routed to your recipient's RCS backend.
That's true, and I'm not a big fan of that either, I'd like to not have to rely on Google as well, but they do interoperate with other providers (for example with my provider) because it's a standard. I don't see how they discontinue RCS unless the whole standard fails to succeed, which seems unlikely.
And since they encrypt the messages, I see less of an issue with them providing the service, it's just store-and-forward of data they cannot read. Of course it would be best if every provider implemented RCS on their own and the Google backend would not be needed, but most of them dragged their feet until Google stepped in and enabled it for the rest of the world.
I don't think it's fair to lump RCS support in GMessages in with the rest of their products, even though I'm also skeptical of any product launches by them these days because they have a bad track record.