Android
The new home of /r/Android on Lemmy and the Fediverse!
Android news, reviews, tips, and discussions about rooting, tutorials, and apps.
🔗Universal Link: !android@lemdro.id
💡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: !askandroid@lemdro.id
For fresh communities, lemmy apps, and instance updates: !lemdroid@lemdro.id
📰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 !askandroid@lemdro.id.
-
Describe images/videos, no memes: Please include a text description when sharing images or videos. Post memes to !androidmemes@lemdro.id.
-
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
- !askandroid@lemdro.id
- !androidmemes@lemdro.id
- !techkit@lemdro.id
- !google@lemdro.id
- !nothing@lemdro.id
- !googlepixel@lemdro.id
- !xiaomi@lemdro.id
- !sony@lemdro.id
- !samsung@lemdro.id
- !galaxywatch@lemdro.id
- !oneplus@lemdro.id
- !motorola@lemdro.id
- !meta@lemdro.id
- !apple@lemdro.id
- !microsoft@lemdro.id
- !chatgpt@lemdro.id
- !bing@lemdro.id
- !reddit@lemdro.id
Lemmy App List
Chat and More
view the rest of the comments
So all the apple simps who always said Google refused to do this, what's your retconned excuse now?
We don't know any details. Google is trumpeting a success and indicating a willingness to assist but it doesn't really tell us much of what it will look like. Apple is committing to RCS, the industry standard as it is (and I assume will be as I hope it breathes new life into the standard...) and not Google's current RCS + proprietary bits implementation.
When MS created a Windows Phone YouTube app, Google blocked it with requirements that were either arbitrary (it needs to be HTML5 for example despite iOS and Android apps being native) or impossible to meet. (requiring specific access that Google would not provide)
So while Google framed it as "Microsoft just needs to do X, Y, Z and it'll be all good!" - sounds good but it intentionally made said requirements impractical or impossible to complete.
Since Google's been conflating their RCS implementation with RCS the standard, I think it'll be a funny (if unfortunate) monkey's-paw result if Apple's adopts RCS completely as the backup to iMessage but continued carrier and Google implementation fumbling results in no change and the iPhone having to resort to SMS/MMS anyway.
(see: a while back when AT&T's RCS could only be used between a couple AT&T Samsung phones - but I do hope it's different this time, I got a group chat I rather take off Instagram.)