Android
DROID DOES
Welcome to the droidymcdroidface-iest, Lemmyest (Lemmiest), test, bestest, phoniest, pluckiest, snarkiest, and spiciest Android community on Lemmy (Do not respond)! Here you can participate in amazing discussions and events relating to all things Android.
The rules for posting and commenting, besides the rules defined here for lemmy.world, are as follows:
Rules
1. All posts must be relevant to Android devices/operating system.
2. Posts cannot be illegal or NSFW material.
3. No spam, self promotion, or upvote farming. Sources engaging in these behavior will be added to the Blacklist.
4. Non-whitelisted bots will be banned.
5. Engage respectfully: Harassment, flamebaiting, bad faith engagement, or agenda posting will result in your posts being removed. Excessive violations will result in temporary or permanent ban, depending on severity.
6. Memes are not allowed to be posts, but are allowed in the comments.
7. Posts from clickbait sources are heavily discouraged. Please de-clickbait titles if it needs to be submitted.
8. Submission statements of any length composed of your own thoughts inside the post text field are mandatory for any microblog posts, and are optional but recommended for article/image/video posts.
Community Resources:
We are Android girls*,
In our Lemmy.world.
The back is plastic,
It's fantastic.
*Well, not just girls: people of all gender identities are welcomed here.
Our Partner Communities:
view the rest of the comments
GrapheneOS actually has a built in PDF reader. Open the "Apps" app if it isn't installed. Look for "PDF Reader" and make sure its installed.
My Android /e/os, a fork of lineage os, also has a built-in one.
So yeah OP, I guess the question is, why does your phone not have a built-in PDF reader, not why android doesn't have one :D
I think I might be using the wrong terminology, forgive me. What I mean is, in my case, why does the PDF have to open in PDF reader instead of directly in the browser (like on iPhone)? That's what I mean when I say "opening things externally."
It doesn't have to, but GrapheneOS is designed around security first, privacy second, and usability third
If you install Fennec browser on it and open, e.g., https://www.learningcontainer.com/download/sample-pdf-file-for-testing/?wpdmdl=1566&refresh=6697dcd62a0141721228502
The PDF will display inside Firefox
The default web browser on GrapheneOS, Vanadium, doesn't parse PDF's (they're an incredibly insecure format) and passes them off to a sandboxed, hardened app specifically for that usecase
This allows rejecting more permissions than doing it in the same process
I think it's a fundamental design question. Apple wants users to do everything within their ecosystem, so they internalize as many functions as possible, whereas Android was designed to be lightweight and modular. Everything you don't absolutely need in a browser just clutters it up.
Personally I like the flexibility of using exactly the app I want for functions rather than having my OS enforce a default.
It doesn't need to be opened with any specific app. Android lets you set default apps for different file types (this is determined by the ending file name characters after the "."). Since you're on GrapheneOS, you're probably privacy-conscience and would be wise to stick with the app included with the OS. This behavior contrasts a user who heads to the Play Store and goes with any PDF reader willy-nilly.
The default app is unusable. There's literally no scrolling functionality. You have to tap a button to change pages
Apple is a bit like Microsoft in that regard. Their browser (safari) is so tightly integrated into their operating system that removing it is basically impossible. Due to that, they can use/abuse it for basic functionality like a pdf reader instead of creating a separate app for it.
Android, on the other hand, doesn't even have a real default browser. While Chrome ships as the default since android 4, it's basically just the app tacked on top. Since PDF readers on android existed before Chrome became the default, Google was never really bothered with including a build in PDF reader in their browser. It simply wasn't necessary. And since most browser depend on chromium, which lacks this functionality, they don't have it either.
Firefox on Android has the option to open PDFs, so if you want it, that would be an option. It isn't a limitation of the operating system, Google simply couldn't be bothered and most others just use copy + past on Chrome.
That makes total sense, now I get it. So all in all, it's more secure to have separate apps doing the job instead of jamming it all into an ecosystem?
A browser is also an app, it's not embedded into an OS.
In some it comes preinstalled, which is the case for safari in ios.
Also, some browsers just happen to include a PDF reader, but not all had or currently have.
As @[email protected] mentioned, Android is meant to be lightweight so it can run in several configurations of hardware.
Most OEM do include a browser in Android, this usually being Chrome. GrapheneOS is basically just Android (in this context) so it doesn't include a browser or a PDF reader, but both are available as a dedicated app from the GrapheneOS team or with any other app you want, for example I use readera, or sometimes Firefox.