Question for developers!
How exactly does the iCloud API work? Has anyone had a chance to really dig into it?
Do you have access to the entire iCloud? Because if so, then the "developer created iDisk equivalent" speculated above would be very possible. Joe Shmoe could create a "Filesystem for iCloud" app, allowing you to view pages files, numbers files, keynote files, and all other files of iCloud enabled apps on your devices. The only difficultly I could see is many apps could use unique formats so they may not be compatible with the viewer in the filesystem app.
The way I originally anticipated the API's functioning is you could link them to your own apps and that is it. Like say I created a note taking app called "iNotes R Us" for iPhone, iPad, and Mac. I would use the iCloud API to link my apps to my individual iCloud "slot" (say position AAABBBC). Each app I create would link to that AAABBBC slot to keep all devices in perfect sync with each other. I don't have access to anything else in the iCloud, my App is for my app files. Of course under this system I could still foresee building an arrangement with another app developer like QuickOffice. Or maybe partnering with a Mac App developer if I didn't decide to create my own Mac App. Then I would share my slot AAABBBC with him and he could share his slot DDDEEEF with me. Now both of our apps can be in sync with each other and it would be up to us to make sure the files are compatible.
That is how I had envisioned it. No one with access to the entire iCloud (except for Apple if they had decided to make an iCloud app). Of course it would be possible for an app like Dropbox, or goodreader, or readdledocs to try to gain partnership with as many popular apps as they can to try to create a pseudo iCloud database.
How exactly does the iCloud API work? Has anyone had a chance to really dig into it?
Do you have access to the entire iCloud? Because if so, then the "developer created iDisk equivalent" speculated above would be very possible. Joe Shmoe could create a "Filesystem for iCloud" app, allowing you to view pages files, numbers files, keynote files, and all other files of iCloud enabled apps on your devices. The only difficultly I could see is many apps could use unique formats so they may not be compatible with the viewer in the filesystem app.
The way I originally anticipated the API's functioning is you could link them to your own apps and that is it. Like say I created a note taking app called "iNotes R Us" for iPhone, iPad, and Mac. I would use the iCloud API to link my apps to my individual iCloud "slot" (say position AAABBBC). Each app I create would link to that AAABBBC slot to keep all devices in perfect sync with each other. I don't have access to anything else in the iCloud, my App is for my app files. Of course under this system I could still foresee building an arrangement with another app developer like QuickOffice. Or maybe partnering with a Mac App developer if I didn't decide to create my own Mac App. Then I would share my slot AAABBBC with him and he could share his slot DDDEEEF with me. Now both of our apps can be in sync with each other and it would be up to us to make sure the files are compatible.
That is how I had envisioned it. No one with access to the entire iCloud (except for Apple if they had decided to make an iCloud app). Of course it would be possible for an app like Dropbox, or goodreader, or readdledocs to try to gain partnership with as many popular apps as they can to try to create a pseudo iCloud database.