[Jeff Campbell]

http://www.appleinsider.com/article...g_for_ipad.html

"Apple is dramatically rethinking how applications organize their documents on iPad, leaving behind the jumbled file system and making file access between the iPad and desktop computers seamless."

Basically it works the same as the iPhone does: apps will store all their documents within their own directory, so when you delete the app, you delete the files. But they will also let you specify which documents you want to share wirelessly. In doing so, the iPad can be mounted via WiFi and you can drag and drop the files back and forth between the iPad and your computer. There will also be syncing capability via iTunes and/or MobileMe, but those details haven't been sorted out yet. Basically they are making it easy for the average person to move things around without having to learn any file hierarchy, which to me is a pain anyway. The storage capacity doesn't sound like much, but to be honest, I have the 32GB iPhone 3GS and I have yet to run up to the storage limit. I imagine it would be the same with this device. But it sounds like a pretty good system of being able to move files in case I do happen to hit the wall.Â*

[Jeff Campbell]

http://www.appleinsider.com/article...g_for_ipad.html

"Apple is dramatically rethinking how applications organize their documents on iPad, leaving behind the jumbled file system and making file access between the iPad and desktop computers seamless."

Basically it works the same as the iPhone does: apps will store all their documents within their own directory, so when you delete the app, you delete the files. But they will also let you specify which documents you want to share wirelessly. In doing so, the iPad can be mounted via WiFi and you can drag and drop the files back and forth between the iPad and your computer. There will also be syncing capability via iTunes and/or MobileMe, but those details haven't been sorted out yet. Basically they are making it easy for the average person to move things around without having to learn any file hierarchy, which to me is a pain anyway. The storage capacity doesn't sound like much, but to be honest, I have the 32GB iPhone 3GS and I have yet to run up to the storage limit. I imagine it would be the same with this device. But it sounds like a pretty good system of being able to move files in case I do happen to hit the wall.Â*

[Dyvim]

I was really excited when I heard about the file sharing, but disappointed once I learned the details. What I was hoping for was a single shared file directory that all apps could access. This is the folder that would mount on your PC when the iPad is connected. This would allow you to seamlessly view or edit the same doc in multiple apps. Why? Because maybe some apps are better at certain tasks. You might prefer viewing Word docs in DocumentsToGo but editing them in Pages or what not. Having a single shared folder would make this simple. Now we still will have to resort to kludgy work-arounds to make one doc available to multiple apps (like storing it as a mail attachment or putting it in iDisk if you have MobileMe and better hope the app you want to use supports accessing iDisk which puts an unnecessary strain on developers- why should a word-processing doc need to contain code to access iDisk?). Also, if I can view Word documents in multiple apps, I certainly don't want all my documents deleted from the device when just one of those apps is deleted. Grumble, grumble. IMO Apple messed this up again.

[Dyvim]

Also, my 32 GB iPhone is nearly full. I would have been happier to see 32/64/128 GB sizing. 64 GB max is disappointing when you consider that last year's iPod Touch has 64 GB and last year's iPhone has 32 GB.

But I imagine for many people, the space will be workable. esp. since Apple is insisting on limiting the functionality of the device. Less functionality means less need for storage.

[ptyork]

Originally Posted by Jeff Campbell

Basically they are making it easy for the average person to move things around without having to learn any file hierarchy, which to me is a pain anyway.

I find this whole notion crazy. The real purpose of the limitation is Apple's need to control the conduit. I've little doubt that the conduit will almost certainly require MobileMe (i.e., I'll be surprised if you can really manage all of this via iTunes), which of course is just another way to upsell. But that's not really the point. Easier? No way! I get the value in hiding the OS and app binary files, but documents/media files are just that. I'm in agreement with Dyvim that a single documents folder that would mount when the device is attached (or could be shared or synced via a cloud service) is the obviously correct way to do this.

Also keep in mind that this is taking a marked step backwards. We've been moving towards topical content grouping rather than task-based content grouping. You create folders corresponding to events or projects or dates and group all files related to those topics together regardless of the tool used to read and/or edit them. Do you store your work-based files (say a proposal) along side your personal stuff (say a party guest list)? Do you have a "Pages Docs" folder and a "PDF Docs" folder? If so, you're no doubt in the minority. It kinda works for media files because they are consumption-only, but it breaks down fast when you're trying to create and manage content. Especially when the amount of content grows beyond just a few files. IMO, this is the biggest problem with stove-piped cloud applications and of course is why even Google has opened up their Google Docs "file-system" to be arranged as needed.

And as Dyvim points out, this removes the ability to use a best of breed (or best for purpose) app to view/edit an application since they are associated with (and available to) only one app (at least without jumping through crazy hoops). Wanna use Photoshop or some other photo management tool to arrange and edit your photos. Okay, fine, but you're going to have to double or triple the amount of space used since they need to be physically copied to that app's "folder." Want to view the edited/cropped file using the standard Photos app? Good luck.

While this concept is grudgingly accepted (though still misguided) on a small, generally limited-use, consumption-only device like the iPhone, it is most certainly not going to be acceptable for a device with higher expectations with regard to content creation and manipulation. And if your comeback is that this IS intended to be a device solely for casual consumption, why did Apple spend millions of dollars creating the iWork apps for this device? The answer of course is that they knew expectations for a device of this size and power would be higher. They just missed the boat in enabling the device to efficiently serve this purpose.