3 ms·

A unified documents folder just doesn't work as seen on OSX. Most filetypes are bound to a specific application anyway, so there's no point in a cluttered unifi

A unified documents folder just doesn't work as seen on OSX. Most filetypes are bound to a specific application anyway, so there's no point in a cluttered unified folder.

extension 16y ago
Why would it be cluttered? It could work just like Settings. Apps with their own document type register as such with the OS. The "Documents" app shows a list of those apps and each one leads to a list of documents for that app. From this list, users can open, rename, delete, attach to an email, and so on. Apps would not be allowed to dump internal junk in their document folder, only stuff the user creates and knows exactly what it is. As long as this model was enforced by the OS and by app reviewers, it should be easy for anyone to understand. It would give iOS something fundamental that Android doesn't have at all, which it really needs because it's playing catch-up with most other features right now.
- haribilalic 16y ago
  If documents are categorised by apps, why have a separate browser for them instead of keeping them in the app? If I want to view my Pages documents, I'd open Pages not Documents or whatever it might be called.p
  - extension 16y ago
    Lots of great reasons: 1. The user can manage all their stuff in one place with consistent functionality across all apps. 2. The OS can implement generic file handling features like search, share, backup, sync, etc. 3. It paves the way for standard file types that can be handled by multiple apps, or apps that can work with any type of file, like Dropbox. The power of filesystems is well understood and I'm sure Apple could create one instilled with their magical UX and just-worksiness. But they won't do it because I think they are afraid of 3rd party apps becoming too useful. They don't want anyone else creating an ecosystem that they don't control. But Google and RIM are happy to do that and I hope they establish a higher standard of utility that Apple is forced to live up to.
WiseWeasel 16y ago
Many file types can be opened by several different applications, and using the Mail app to transfer them from one app to another as we do now is simply an awful, awful kludge. If I'm looking for a file on my iPhone, I'd much rather have a central document repository to look through than to have to dig through a bunch of emails to find the attachment in question, or use a bunch of unique app interfaces with their own document management implementation. This limitation is so obvious that I'm surprised anyone would actually think the status quo is acceptable, let alone advantageous.

A unified documents folder just doesn't work as seen on OSX. Most filetypes are bound to a specific application anyway, so there's no point in a cluttered unified folder.

extension 16y ago

Why would it be cluttered? It could work just like Settings. Apps with their own document type register as such with the OS. The "Documents" app shows a list of those apps and each one leads to a list of documents for that app. From this list, users can open, rename, delete, attach to an email, and so on. Apps would not be allowed to dump internal junk in their document folder, only stuff the user creates and knows exactly what it is. As long as this model was enforced by the OS and by app reviewers, it should be easy for anyone to understand. It would give iOS something fundamental that Android doesn't have at all, which it really needs because it's playing catch-up with most other features right now.

haribilalic 16y ago
If documents are categorised by apps, why have a separate browser for them instead of keeping them in the app? If I want to view my Pages documents, I'd open Pages not Documents or whatever it might be called.p
- extension 16y ago
  Lots of great reasons: 1. The user can manage all their stuff in one place with consistent functionality across all apps. 2. The OS can implement generic file handling features like search, share, backup, sync, etc. 3. It paves the way for standard file types that can be handled by multiple apps, or apps that can work with any type of file, like Dropbox. The power of filesystems is well understood and I'm sure Apple could create one instilled with their magical UX and just-worksiness. But they won't do it because I think they are afraid of 3rd party apps becoming too useful. They don't want anyone else creating an ecosystem that they don't control. But Google and RIM are happy to do that and I hope they establish a higher standard of utility that Apple is forced to live up to.

WiseWeasel 16y ago

Many file types can be opened by several different applications, and using the Mail app to transfer them from one app to another as we do now is simply an awful, awful kludge. If I'm looking for a file on my iPhone, I'd much rather have a central document repository to look through than to have to dig through a bunch of emails to find the attachment in question, or use a bunch of unique app interfaces with their own document management implementation. This limitation is so obvious that I'm surprised anyone would actually think the status quo is acceptable, let alone advantageous.