The Problem of Uploading

How to get your files up.

After reading about Fluxiom on Techcrunch I thought about different ways of uploading files to a web server. I will try to rate them in accordance for usage in a web application.

HTTP

The classic: Build a web form, instert a browse…-button, submit, process data and your done. While beeing great in uploading a couple of files it becomes pretty undhandy when dealing with large files or mass uploading. Even at MySpace they use it to upload your songs and it feels quite cumbersome.

• Great when dealing with small and single files.
• Horrible when it comes to large files. The browser needs to stay open.
• Even worse in mass uploading: Did you ever tried to select a hundred files manually from your computer? I don’t think so.
• Users need feedback on the upload progress.

Zip Archives via HTTP

Zip archives are great: They are part of most modern operating systems and the de-facto standard for file compression.

• Good: File sized can be reduces dramatically.
• Good: Merge multiple files in single one.
• Bad: Complicated workflow. Search your files locally, archive them and upload. Seems to be too many steps.
• Bad: One has to implement server side zip extraction. Okay, it’s quite easy, but it will cost time.
• Worse: It’s still HTTP (see above)

FTP

FTP sounds like an obvious candidate for uploading files. But when going the web app route you have to remind yourself chances are, your audience has never heard about FTP.

• Most people – even tech savy – are not comfortable in using a third party programm.
• Configuration: entering server, username and password is way too much.
• It will not feel like their trusted operation system environment.
• People will mess up: special characters, slashes, permissions.

A Drop Box

The most promising approach. Flickr uses it and now also Fluxiom. A simple Application where you throw your files at and everything else is done automatically.

• Must-have: Zero / Easy-Configuration. Enter username/password and you’re done.
• Great: The easy road. Let users work in their existing OS, process data when user logs in next time.
• Bad: 2 Steps. Uploading and giving your data context are seperated.
• Of course one would have to build it supporting Windows and OS X.

Conclusion

When building a web app you have to consider different scenarios when it comes to uploading files.

• HTTP is good when you have small chunks of data,
• ZIP files just don’t feel right (in terms of workflow),
• FTP is good (but geeky),
• Drop boxing is best (Drag’n Drop, and you’re done), but might be overkill in implemtation.

So what do you think? Did i miss a point here? Are there other ways one might think of?

The end is near, now what to do?

Please let us now what you think about this artice by commenting it. You can respond from your own site using our trackback url: The Problem of Uploading. You may want to follow new entries by subscribing to our RSS Feed. Our just browse our weblog and check some other articles.

• View all posts

7 Responses to “The Problem of Uploading”