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
I've seen this a lot lately on lemmy - that android needs "saving" or that we need government intervention to stop Apple. But, I would argue that android is its own worst enemy. Even the best android phones are plagued by quality issues, both hardware and software. Google's own pixel lineup has seasonal class action lawsuits over build issues, and now they automatically opt you into non-arbitration agreements whenever you activate a new Google phone.
Personally, I'm willing to take the risk because, in my experience, stock android is just so much better than iOS (and other android flavors). But therein lies the issue - android could compete with iPhone just fine, but android manufacturers can't (or won't) compete with apple's relentless pursuit of build quality and software polish. Another damning aspect of this is that Google is supposed to be the best software company in the world, yet they've taken more than a decade to figure out messaging - something apple figured out back in ~2010. Android doesn't deserve to claw back market share in the US until their phones are actually better per $ than the iPhone.
¯\_(ツ)_/¯
As somebody who has professionally done software for Android (and iOS and a lot of other things all the way back to very early dynamic websites with CGI-script backends) I would say that the biggest enemy of Android is the increasing bloat of each new version of the framework as it was not designed well to begin with, has "evolved" by layering stuff on top of stuff and has had multiple changes in the way it's supposed to be used (in the professional lingo, "at the technical architeture level") so it's been a bloated mess for a while.
The result is a slower OS which uses more memory and storage and ditto for apps made for it, and they've even managed to fragment the developer community (by adding a 2nd programming language, for no reason other than to copy Apple in doing so) and frankly I see no sign at all that the bloatware-framework trend will stop, much less reverse (my - granted, limited - experience with Google Technical Architects is that they're not really qualified at that level)
No you have it wrong, we just haven't implement clean architecture with usecases, it'll be different this time I swear, just wait until Google IO...