#TODOLICIOUS MAC OS#

Similarly, if I were to build a web app version of Todolicious (which I was planning on), I could not get access to that data within iCloud at all. But if I back Todolicious with iCloud, I have no way of speaking between my server and iCloud (and I’d still need a server of some kind to send the notifications, after all). With the sync server I was building, this was fairly trivial wait for the user’s list to change, and send a signal to push the count everywhere. When you tap a To Do to mark it as done, suddenly all your devices would show the correct number on the icon. In my To Do list app, Todolicious, one thing I would love to be able to do is to push badges to your iPhone and Mac showing the number of To Dos you have left. Here’s some examples of what I’m talking about. If you sync data through iCloud, And, you will never be able to have a server component that can do things with your data all the time. You will never be able to port it to Android, WebOS, Windows Phone, or the web (mobile or desktop). If you build an application targeting iCloud, you can only ever put it on two platforms – Mac and iOS. This has a few interesting practical repercussions. So the only way for developers to move their data through this system is through a pre-compiled bundle that gets referenced within an application. Under the hood, they are obviously talking to the network and doing the business of syncing data, but that networking layer is not exposed or documented, and would have to be reverse-engineered in order to understand and use.

#TODOLICIOUS MAC OS#

Right now, the only way to access it is through Objective-C APIs embedded into iOS and Mac OS X. This is inherently a good thing, and it will open avenues for many new types of apps. ICloud looks like it will be an incredible technology for moving app data between devices.