Android

17683 readers

22 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]

Google merging Pixel, Nest, and Fitbit teams under one hardware umbrella (www.androidauthority.com)

submitted 10 months ago by [email protected] to c/[email protected]

2 comments fedilink hide all child comments

More layoffs associated with it

top 2 comments

sorted by: hot top controversial new old

[–] [email protected] 12 points 10 months ago (1 children)

I don't think this is necessarily a bad thing. Google struggles with presenting a unified interface, design language, and overall experience across their scattered hardware platforms. Google's hardware has had the feel of the left hand not knowing what the right hand is doing.

However, time will tell whether this is truly a refocus on what's important or merely an organizational device to cut headcount at the possible expense of long-term development.

[–] [email protected] 3 points 10 months ago

Google struggles with presenting a unified interface, design language, and overall experience across their scattered hardware platforms

Agreed, but that to me seems more of a conceptual and software issue, rather than the hardware side. Although the article makes it seem like the teams getting merged are also (at least partially) responsible for that:

Currently, all three teams operate separately, making standalone decisions on things like design, software, hardware engineering, etc.

However they also need to be more reliable to build an ecosystem that people buy into. It's kind of a meme that in every google thread killedbygoogle.com gets mentioned, but there is truth behind it. Especially in the smart home space you really need to project long term support for people to buy into your product suite.