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
Oh no? We've had browser storage and cached web apps for twenty years now. The technology exists and could be improved, if we stopped forcing everything to be a native app.
I mean, honestly, most "native" apps are webviews displaying cached content. Clearly we can make it happen, it just needs to be more discoverable and have smoother integration.
So you're just reimplementing the current model but with the extra layer of a browser in between. Installing a PWA is the same as installing a native app, except instead of running it directly you also have to have a browser installed to run it. It's adding a significant amount of complexity for no good reason. Browsers are huge attack targets.
No, I'm removing the layer of the native code that launches whatever flavor of Electron they're running under the hood in favor of the browser and webview that's already installed on your device (or whatever other one you're interested in switching to).
...which literally every single mobile device already has. Seriously, you can't uninstall webview if you wanted to.
Plus, you only have to install one browser for the entire system, Come on. You can't honestly believe that the dozens of reproduced copies of the same codebases that live on your phone right now are a good use of your phone's storage or memory.
I don't know what complexity you think it's adding. It's removing a bunch of native code, and replacing it with web-standard code that (in the case of most apps) was already written for the native app anyway, or at least was written for the web app.
Ever wanted to mod an app? If it was a web app running in a browser, you could. Would you like to use ad blockers on the YouTube app? Or use a userscript to hide stories about a particular person? Or automate the function of one of your apps? With native code you can't. With web apps you can. Web apps are more accessible, they adhere to published standards, they're not as heavy on your operating system, they're more resistant to privacy-siphoning attacks and surveillance, they're more easily able to share code...and, to be honest, they're also easier to develop. The only reason for corpos not to do this is because it gives the user power that they would rather be able to sell to the user instead.
Security is not improved by forcing users to switch to native apps. For one thing, most companies' apps already are web apps; if they're not already hardened, wrapping them in native code and putting them in the Play Store or App Store won't magically make them more secure, because decompiling native apps and sniffing API endpoints is still a thing. Also, it could be argued that browsers are more resistant to security issues, since you can patch them once and mitigate certain vulnerabilities in every app without waiting for developers to ship a fix.