Photo credit: geeky-gadgets.com
iCloud is a big deal for me, and, I believe, for lots of other developers out there as well. Syncing data has become a lot easier with this new service and the according APIs. I once took a glimpse at the MobileMe syncing APIs and my head still spins a little.
What does it mean for flickery?
I’m still thinking of the implications for flickery. I got some nice ideas from users of flickery on twitter and I’m already looking into what is possible and makes sense in terms of flickery.
I could see flickery syncing the items yet to be uploaded or loocking into iCloud’s photo queue and offer an option to upload those items or at least present them in some way in flickery’s upload view.
What does it mean for ScreenFloat?
For ScreenFloat, In a nutshell, it will sync your shots between your devices (I don’t know if a iPhone/iPad version of ScreenFloat is useful, but I’m certainly entertaining the idea of having the shots on, say, your iPad, as well).
It will sync which shots are currently open and floating, which are hidden, which are in your shots browser, it will sync your categories in your shots browser, and their contents.
This is something I wanted to do from the beginning and I’ve been looking into services like DropBox to implement it. Now with iCloud (and yes, I realize it’s still a few months away) it’s even easier, faster, more reliable and more secure to implement.
What does it mean for GimmeSomeTune?
I don’t believe GimmeSomeTune could have any advantages of iCloud in terms of sync. If you find one, leave a comment or write me an e-Mail :)
I have an upcoming app where iCloud will be perfect and will replace a server-client environment with tedious networking stuff. Stay tuned on that :)
My good friend and honored developer colleague Christian Kienle wrote about the impact that iCloud may have on his applications on his blog.
It’s an interesting read, especially if you’re interested in how you will benefit from iCloud in the near future.