Android

19849 readers

460 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: !askandroid@lemdro.id

For fresh communities, lemmy apps, and instance updates: !lemdroid@lemdro.id

💬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 !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

Lemmy App List

See thread

Chat and More

founded 2 years ago

MODERATORS

ijeff@lemdro.id

ladfrombrad@lemdro.id

Paradox@lemdro.id

multimoon@lemdro.id

mikestevens@lemdro.id

Devgard@lemmy.world

limerod@reddthat.com

Netrunner@lemdro.id

150

Google confirms it's 'combining' Chrome OS and Android into a single platform (www.androidauthority.com)

submitted 2 weeks ago by baronvonj@lemmy.world to c/android@lemdro.id

45 comments fedilink hide all child comments

Sameer Samat, president of Android ecosystem at Google, asked a TechRadar journalist why they were using an Apple Watch, iPhone, and MacBook:

I asked because we’re going to be combining Chrome OS and Android into a single platform, and I am very interested in how people are using their laptops these days and what they’re getting done.

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

[–] skuzz@discuss.tchncs.de 0 points 6 days ago

Android also is designed to run on lots of different hardware unlike Apple.

Apple's OSes are also designed to run on lots of different hardware. Intel, PowerPC, ARM, nVidia, AMD, Apple GPUs. It is just all hardware Apple (mostly these days) designs. There's no reason to talk about what hardware they run on. We're talking about their parallel roadmaps to closing off the OS development from users/open-source, and how both are doing the exact same transition, Apple's is just a quarter century in the making.

Google has already been doing what is necessary to close Android for years. Example: The AOSP texting app they abandoned years ago. Google Messages is now the messaging app. Fully closed-source. No requirement to ever open it. They also used RCS as an excuse to close off the third-party messaging app arena. No third-party app can use RCS on Android now.

Play Services, Assistant, Chrome, YouTube, YouTube Music, GBoard, all their applications are being separated and the "old" version phased out. Some things will remain open-source, likely, like the Chromium bits of Chrome, but even that they've already forked their secret Chrome sauce.

With a hybridization of ChromeOS and Android, this will further accelerate Google not having a need to care about the existence of AOSP. Eventually, they'll just abandon it entirely.

If you use an AOSP-based OS like Graphene right now, you can see the remnants of the AOSP apps. Peeps on projects like Graphene do some massaging to keep them usable, but they're basically apps frozen in time to aid companies in proof-of-concepts and not part of what one would call consumer-facing Android today.

Vendors like Samsung and Lenovo pay to have early access to the Android source, so they'll still get early access for device development, but it is a 100% pay-to-play model. Likely with NDAs. Which again, is exactly what Apple does.