iPhone OS 4.0
ignorethecode.net
ignorethecode.net
The task switcher lets you switch back and forth between apps one handed using your thumb. I think that's part of the rationale for it. Also, the Least Recently Used algorithm will dynamically make a short list of the actually used apps in a user's collection. Most users probably spend 80% of time in a small minority of their apps.
In this case, the real alternative to the task switcher is flicking through multiple pages of apps, which surely is more difficult than a simple row of recently used apps. It's hard to imagine a pinching gesture that would be usable here, without interfering with the current app.
However, if a user is switching between three or four apps for a given period of time, those apps may very well lie on very different pages of the Springboard. The most frequently used apps are not always the apps that matter now.
Even when you would need to swipe in the task switcher, surely it is easier to find an app among 4 instead of 16?
(Maybe the task switcher really is only useful for a small subset of use cases, in which case your position would seem to be the logical one.)
In 4.0, it works just exactly like in Safari: as long as the app don't get killed from the task switcher, its state are resumed automatically.
Android uses a separate and almost useless alphabetically-sorted application's drawer. You are able to put applications on the home screens, but chances are that you are messing with an application that you don't use very frequently and thus have not placed it onto a home screen. In addition, on stock Android (not rooted/jailbroken), you only have 3 home screens.
I think others have mentioned that you can get 3rd party apps for Android that increase the number of home screen to at least 7. These do not require rooting or anything else unusual, just a quick download from the Market.
«I think it’s fair to say that most people involved in interaction design tend to agree that hierarchical file systems have largely failed their users. […] However, when we say ‹hierarchical file systems don’t work›, most of us end that sentence with ‹so we need to replace them with something better› in our heads. Apple, on the other hand, ended the sentence with ‹so we’re not going to bother with this stuff, let’s just leave this up to each individual application.›»
There are even applications for which hierarchical organization is entirely appropriate at the UI level: An obvious example is an outliner. And it's not a coincidence that our filesystem UIs have little icons of file-cabinet drawers and file folders: The real world features file cabinets and folders, and people have traditionally been able to make sense of those, hierarchy and all... in a context which naturally fits into a hierarchical scheme.
It's worth asking whether the cardinal sin of the hierarchical file system isn't the fact that hierarchical is innately confusing, but that for thirty years and more programmers have labored to fit non-hierarchical problems into a hierarchical paradigm, often in totally unnatural ways. Replacing that One True Paradigm with another One True Paradigm might just prolong the fundamental mistake.
Interesting to note how it's done on the iPad: Photos, for example, are stored in a hierarchy (in certain views at least; there's not a strong sense that the "true" scheme they're stored in is an hierarchical one), but no folder metaphor is used. It's just stacks of images.
Likewise, the "folders" in OS 4.0 are that in name and function only. They are represented more like the stacks of photos, though the objects "in" them are shown as tiled (with a linear view when tapped, for easier picking) rather than overlapping, though, in that case. But an opaque container isn't used.
So, in both cases, the objects are collected without the container being drawn attention to.
This may limit the number of levels of hierarchy that are possible (stacks of photos within stacks of photos would break the metaphor... not that people put real-life folders within folders very often), but most users don't like deep hierarchies anyway, and the extra hierarchy of objects being stored "within" apps helps mitigate that as well as segregate things somewhat naturally by type.
Of course certain tasks will always require deep, complex hierarchies.
When you have to drill down through more than a few levels of hierarchy to get to what they want, it becomes confusing to keep track of, especially because folders create groups of arbitrary types so everyone has to build their own hierarchical system for each type of data. So while my nested folders for photos represents year/month/event my nested folders in my music library mean artist/album and my Documents folder is a mess where I try and make up groups of things I will remember again later. "does this piece of writing belong in my Essay folder or in my Journal folder?" Who can say? and if I pick one now, what's to say when I go looking for it later I might not categorize it differently?
Things like iPhoto make those decisions for you, just add your pictures to it and it will make you group them as an event, and that is all you have to do. iPhoto actually lets you look for photos in several different ways then: hierarchically by year/month/event, event in overall order, by who is in the picture, or where it was taken. That is a lot of flexibility that lets me search for a photo in whatever way I'm thinking about it in the moment, rather than having to search for a file based on however I originally decided to organize them on the file system.
A straight hierarchical file system is pretty limiting: it only allows you to find files based on one organizational method. That's why search is becoming so useful and why tagging seemed like such a good idea. It would be great if we could find out what the best way for me to keep track of my writing is without me having to think about how it is structured on disk.
So I guess what I am trying to say is that I agree with you that we need different organizational methods for different pieces of data, and that I think nested "folders" is going to be the right solution very rarely. And I agree with Lukas that there needs to be a lot of work done to help people share files and move files to and from the iPad easily.
"When good interfaces go crufty"
"So, the Mac’s designers invented something called a “file selection dialog”, or “filepicker” — a lobotomized file manager, for opening and saving documents when the main file manager wasn’t running."
http://web.archive.org/web/20050101092500/http://mpt.phrasew...
The author makes a good point about the difference in icon placements between the folder icon and the folder itself.
For file management, iPhone OS 3.2+ is already half way there. It syncs specific files from one's computer to specific apps. What we need is to extend this and have a system-wide documents database that is akin to the contacts, calendars, and music database APIs. Version control support in this API would be cool as well.
http://macreviewzone.com/archive/hardcider/Reviews/RD9.shtml
Of course, no apps background properly currently, but it's useful for testing.
I'm using it on my primary iPhone, but I carry a backup phone in case I actually need to get stuff done ;)
I only have one iPhone, but I do have iTouch I use to test our app on.
OK, it was kind of passive aggressive of you (the author of the post) to just state this without any explanation backing it up, but I'll bite. Please do give us your rant about how local notifications (introduced in OS 4.0) in addition to the already existing push notifications does not address notifications.
Or maybe you just missed that part?
The article is about the iPhone's user interface, not about the backend; local notifications have nothing to do with the user interface. And I simply assumed that everyone who has used an iPhone knows that the notification UI is very basic; you mostly get modal alert boxes, which are very easy to accidentally discard.
Although, I've had instances when handling bulky folders and moving them around, the top most documents would get accidentally rearranged! ;-)