4 ms·
I've mentioned this a couple of times, but coming from my deeply non-technical niche, I think files are dying and good riddance to them. They're a constant bar
by patio11 17y ago
I've mentioned this a couple of times, but coming from my deeply non-technical niche, I think files are dying and good riddance to them. They're a constant barrier in front of my customers getting their work done and going back to their lives. They're an abstraction which is -- mercifully -- more user friendly than disk sectors or IP addresses, but not by very much: my users may lack the ability to find saved files on the computer, to understand the difference between the filesystems on two computers, to be able to copy a file to a floppy or CD without active moving-the-mouse-for-her assistance, to differentiate between files and the applications that created them (expecting, e.g., that copying bingo cards onto their sister's computer will let them open them automatically -- hey, works for photos and letters, right?), etc, etc. We won't even get started with navigating a tree structure.
I've had a sustained decrease in the amount of time I spend supporting customers with these issues since releasing my web application, because it comports to how many of them think their files actually work: they live in the application, they always exist in the application no matter what computer you're on, they always show up on the top screen no matter what, they never get lost, and even if they get lost Patrick can find them for you if you send him an email.
- stcredzero 17y agoEverything on the iPhone is task-centric, not file-centric. The “file” part of completing tasks is completely insulated from the user. This squares with what you said and with what I saw on the bus last week. A woman with two kids and a Nokia phone was trying to find the video from the school play. First, she went to the apps that were related in her mind, and found nothing. She started to become confused and desperate. (repeating "oh my god" several times) After a long time she said, "Was it File Browser?" She was able to find it shortly after that. Users think in a task oriented way. Our interfaces tend to be implementation oriented, unless we discipline ourselves.
- abstractbill 17y agoFiles are an abstraction that allows multiple applications to operate on the same objects (photos, videos, etc). The argument here seems to be that the cost of the abstraction (user confusion) isn't worth the benefit, and that we should go back to only allowing one application to access each kind of object. I have to disagree. The abstraction might not be perfect, but it does enable something pretty damn useful.
- dcurtis 17y agoNo, no, that's not what I'm saying at all. You have a database in the iPhone called Photos & Videos. You store all photos and videos in there. Then you can open any number of apps -- photoshop, Camera, Photo Viewer, Mail, etc -- and act on those files. Any changes you make will be centrally reflected in all the other apps, since there's only one copy of the file. In the primary app for any particular database, say Photos, you can create albums and organizational structures based specifically on that type of data: Albums for photos, for example.
- pchristensen 17y agoI wish you had said this in your article. This is a pretty good solution for the problem you described. I've been thinking that a standard cloud-app-filesystem-service that any app could register to use would solve the problems with no-user-filesystem .
- stanleydrew 17y agoWait, now I am confused. I thought your article was about the death of files, but you've just mentioned files twice in relation to photos on the iPhone, albeit files within a database.
- abstractbill 17y agoOk, so that's less restrictive than you made it sound in your article. I'm not sure you want to kill files or filesystems at all. In fact, all you want is a filesystem that enforces the restriction that files of a given type should always live under a directory that holds only files of that type. Ok, reasonably interesting. I'm not completely sold, but I can see it has a lot of advantages - it might work! One open question for me: Where do things like zip archives live? They don't seem to have a logical place to be. You also seem to want to rename "filesystem" to "database". I'm not sure why. A filesystem is already a (specialized) database.
- dmoney 17y agoIf you are catering to non-technical users, I would hope they wouldn't have to deal with zip files. Compression could be treated more like metadata, rather than a type of file (i.e. the filesystem transparently compresses them based on usage patterns or preferences). But in general, I think there are two types of files: files needed by a user and files needed by programs. A good solution would make it so that the non-technical user doesn't need to know that the latter kind exists.
- stanleydrew 17y agoYou are right that users think they are better off without files. And I completely agree with you that web applications provide a nice avenue to a life with no files (No access to the local filesystem from within the browser? Great! We'll just store everything in a database on the server). But then we start to have these situations with data lock in that are definitely bad for users. Take Facebook since it's oh-so-popular to bash them these days. If my Facebook data were stored in an encapsulated and portable format I'd just go to a new social network that respected my privacy and say, here's my data, ready to go. Import it. Now it may be the case that most users are willing to turn over their data to the application that created it in exchange for simplicity and ease of use. But I don't think that's a debate that many users are having with themselves right now.
- kaib 17y agoI think you can have your cake and eat it too. A webapp that's task centric can still offer export and import features for power users. You are right that if people stop asking then such a feature might not be provided but at least for now it seems to be more of policy decision on the company part than a hard and fast numbers game.
- stanleydrew 17y agoI agree completely. For what it's worth, I think webapps with import/export functionality are the future for almost all software.
- patio11 17y ago"Facebook would be better if Facebook used files" is a bit of a strawman. [Edit: No, it isn't. Crikey, failing at English: what is the word for an argument premised on a proposition that is contrary to fact? It can't just be "wrong", that's what 3rd graders say -- needs more Latin.] Do you know a single application that abstracts away as much data as Facebook does as files? Anything on my computer nearly that complex, like an email inbox, a photo collection, or my iTunes stuff exists as an opaque blob with a proprietary reader. (In the case of my inbox, it is an opaque blob with widespread inport/export capability into opaque blobs of different colors.) It has a file on disk like MySQL does: OK, technically accurate, but I'm not capable of actually doing any of my usual file activities with that file. That is aside from the "whose data are we talking about, anyhow" conundrum. Probably 80% of my presence on Facebook "belongs" to other people. Tagged in a photo taken by my mother of my brother's wedding: think quick, is that in my export or not? (For that matter, is my brother in my export? I'd kind of like to import him into my new social network. You can do that, right? Oh and Farmville.)
- kaib 17y ago> and even if they get lost Patrick can find them for you if you send him an email. I think this nicely sums up a lot of things about your business. Your users know you by name and trust you (competently) answer their emails .. :-)
- patio11 17y agoAn unfortunate reality of customer service: customers trust me when they have a good experience, and a good experience with Bingo Card Creator means that customer is nowhere near a computer and hence is not emailing me right now. If a customer is emailing me right now, that means they are still on the computer, and if they're still on the devil box, something has probably gone wrong.