Forgive me for this stupid question. I just transitioned from iPhone to Pixel (GrapheneOS) and I’m curious why there isn’t a built in PDF viewer like on iPhone? It feels like you have to open things externally pretty often, but I figure there’s a reason for that. I haven’t used Android in many years and I recently developed an interest for the technical aspects of things, so again, do forgive this beginners question.
Cheers y’all!
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
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.
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?