4 ms·
I don't disagree that iOS handles downloaded files terribly (Safari does notify you when your file is downloading/finished, but in a very subtle way by adding a
by gpt5 4y ago
I don't disagree that iOS handles downloaded files terribly (Safari does notify you when your file is downloading/finished, but in a very subtle way by adding a download icon navigation bar).
However, using an anecdote of an uncommon use case being bad hardly supports the conclusion of your last sentence.
- tomrod 4y agoOpening downloaded PDFs is uncommon?
- elondaits 4y agoiOS Safari opens PDFs directly. It's a file format with native support. I don't know why the OP had to do those steps, as that never happened to me... maybe the site hosting the PDF informed the wrong MIME Content type, so the file was downloaded as a generic "binary" file.
- lultimouomo 4y agoContent-Disposition: attachment.
- 8note 4y agoI'd expect uncommon cases to be where UX simplicity and expected behaviour is the most important? That's when you actually have to guess about what's happening. If the UX falls apart whens you leave the 3 most common patterns, your thing isn't easy to use
- gpt5 4y agoMaybe if you look at uncommon use cases collectively, but not when you just take a single uncommon example (a pdf file with forced download via Content-Disposition: attachment) and extrapolate it to the entire OS.
- TulliusCicero 4y agoAlmost any kind of file management where you need to do something other than use a file created within the app itself is a pain in iOS compared to Android. At least, it was historically, I know more recently iOS has gotten better with exposing the file system to consumers. I really don't think this is an "uncommon use case", people do download files and stuff all the time, people wanna move their files around too.