A lot of my UX guidance I get, I get from my wife. Sometimes she's not like your normal user at all (she used FreeBSD for a year, although as an end user runnin

A lot of my UX guidance I get, I get from my wife. Sometimes she's not like your normal user at all (she used FreeBSD for a year, although as an end user running Gnome). Sometimes she is (she hates the Mac's maximise button not maximising the screen - she also hates having to CMD-Q instead of closing the last window). She loves the iPhone. She finds it easy. She has trouble posting images from her photo album to facebook - does she go to camera, photos or facebook? This is the problem with the app paradigm. It's essentially a variant of the folder hierachy. She can play music from her 'music database' on iPod. Why not on last.fm? (bearing in mind that the average user is not aware when it plays something she owns whether or not it's stored locally or streamed) It sounds as though superficially it makes sense, but without a clear understanding of what owns or uses which database you're still reduced to a folder-oriented paradigm - it's just in this case folders are applications and the data can live under any or all of them.