[{"_1":2,"_30":-5,"_31":-5},"loaderData",{"_3":4},"routes/__layout/tag.$name",{"_5":6,"_7":8},"tagName","web applications","posts",[9],{"_10":11,"_12":13,"_14":15,"_16":17,"_18":19,"_20":21,"_22":23,"_24":25,"_26":27,"_28":29},"id",3,"title","What I just did was important","excerpt","I just used Flickr to batch-resize photos for a friend's website gallery, not because I needed cloud storage or any web-specific feature, but simply because it was the easiest option available. That moment crystallized something: web apps are winning not on principle, but on pure user experience.","body","\r\n\r\n

So, I was making a website as a favour to a friend of mine. The site has a gallery (not published at time of posting). Like any gallery, it has simple needs: a bunch of thumbnail images, and then a bunch of larger images conveniently sized for viewing in a browser.\r\n\r\n

It turns out there are three ways of doing this:\r\n

Manually: open each image in an editor, size it to two different dimensions, save the edited versions. This is slow, boring and laborious.
Using a desktop application: find a batch feature in one of my existing image editors to do it, or get a custom gallery-making program to do it for me. I know Paint Shop Pro has this feature, though it requires a little fiddling to get right. I'm only getting to grips with Photoshop quite late in my web development life (Paint Shop Pro always did everything I needed, and still does, but Photoshop is what Yahoo! has a license for), but I assume it can do this too, possibly involving downloading some sort of macro or something. I'd have to google it to find out.
Using a web service: as it turned out, the easiest way to do exactly what I needed was just to upload the images to Flickr. Flickr automatically produces several sizes of image, including thumbnails that are cropped to better show off the content of the photo. This didn't involve downloading anything and was by far the easiest method. And as a bonus, the Flickr community now has some images of the performers tagged with the event name.

\r\n\r\n

This is important because of what it says about how people will use web applications: not because they particularly need portability or central storage or any of the \"web\" aspects of the service, but because the application is easy to use and does exactly what they want. It's only recently, as average bandwidth has increased and interfaces to services have improved, that it was at all possible that a web service would be a better user experience than a dedicated desktop application. But this is where, eventually, almost the whole application space is going to go. That's been the consensus amongst the kind of people who make it their job to think about these things for a while, but it never really struck home for me until just now.","updated",["D",1163954245000],"created",["D",1163954245000],"codename","what_i_just_did_was_important","legacy_id","3540","published",["D",1163954245000],"draft",false,"actionData","errors"]

Posts tagged “web applications”