Android

17683 readers

17 users here now

The new home of /r/Android on Lemmy and the Fediverse!

Android news, reviews, tips, and discussions about rooting, tutorials, and apps.

💡Content Philosophy:

Content which benefits the community (news, rumours, and discussions) is generally allowed and is valued over content which benefits only the individual (technical questions, help buying/selling, rants, self-promotion, etc.) which will be removed if it's in violation of the rules.

Support, technical, or app related questions belong in: [email protected]

For fresh communities, lemmy apps, and instance updates: [email protected]

💬Matrix Chat

💬Telegram channels / chats

📰Our communities below

Rules

Stay on topic: All posts should be related to the Android OS or ecosystem.
No support questions, recommendation requests, rants, or bug reports: Posts must benefit the community rather than the individual. Please post to [email protected].
Describe images/videos, no memes: Please include a text description when sharing images or videos. Post memes to [email protected].
No self-promotion spam: Active community members can post their apps if they answer any questions in the comments. Please do not post links to your own website, YouTube, blog content, or communities.
No reposts or rehosted content: Share only the original source of an article, unless it's not available in English or requires logging in (like Twitter). Avoid reposting the same topic from other sources.
No editorializing titles: You can add the author or website's name if helpful, but keep article titles unchanged.
No piracy or unverified APKs: Do not share links or direct people to pirated content or unverified APKs, which may contain malicious code.
No unauthorized polls, bots, or giveaways: Do not create polls, use bots, or organize giveaways without first contacting mods for approval.
No offensive or low-effort content: Don't post offensive or unhelpful content. Keep it civil and friendly!
No affiliate links: Posting affiliate links is not allowed.

Quick Links

Our Communities

Lemmy App List

See thread

Chat and More

founded 1 year ago

MODERATORS

[email protected]

The sooner Android accepts RCS is dead, the sooner we can choose the next messaging platform that matters (www.androidpolice.com)

submitted 1 year ago by [email protected] to c/[email protected]

39 comments fedilink hide all child comments

I'm just sitting here frustrated because I'm wanting my family to move away from messaging me over SMS (they mainly use iOS), but they refuse to download any extra apps. But Google's RCS really doesn't look like a solution either since it mainly just seems to be a way of enforcing Android as an ecosystem, and they don't even make RCS available for 3rd party apps to use either.

you are viewing a single comment's thread
view the rest of the comments

[–] [email protected] 46 points 1 year ago (6 children)

Bad take. The problem isn't RCS, it's Apple.

[–] [email protected] 7 points 1 year ago* (last edited 1 year ago)

I think it's complex and the problem have been many things. When Apple pitched an open version of iMessage to the carriers long ago they refused because the didn't like the E2EE. They were surprised when Apple later introduced a proprietary version (and subsequently discovered it was a competitive advantage).

Now there's a Client-server encrypted version of RCS in GSMA but the E2EE version is Google's and running on Google's service. It was only recently that two carriers in the US agreed to use Google's messaging app for interoperability but is E2EE in GSMA?

Interoperability have been a problem as at one point carriers weren't even interoperable while using Universal Profile (I think they are now). Apple surely wont use it unless forced (it makes business sense not to) but between GSMA Universal Profile (which Apple would have to use) and Google's much better version based on the Signal protocol the current situation is also a mess.

load more comments (5 replies)