I dread the thought of dealing with
Apple's MobileMess. Apple has amply demonstrated they can't do reliable cloud services; dotMac was an intermittent disaster for years. They had one chance to show they could do this, and they blew it.
Apple should have delayed the transition. Big mistake.
So I'm even more committed to a Google solution. I'd take a look at Yahoo!, but they're in a corporate death spiral. Heck, I'd take a look at Microsoft, but I'm pretty committed to OS X and they're not.
You can directly subscribe from iCal to a gCal calendar -- I'm going to see if I can fit that into my iPhone workflow. It's not a sync solution however.
Google has a tool to allow Outlook to gCal sync, but they haven't done one for iCal. Given
how bad their Outlook sync launch has been (synchronization is hard, but
Google has issues too), that's no great loss.
There are two commercial alternatives:
Spanning Sync and BusySync. Missing Sync, which we licensed for
Emily's Palm, and
licensed again for her Blackberry, deals with device to machine sync, so they're not a contender. Too bad, they do pretty well.
BusySync is sold as a product, Spanning Sync is a service with a per user license. So for a shared machine BusySync may be less expensive, though that's probably not the licensed use.
Here's what made my trial decision easy however:
- Spanning Sync offers a 15 day free trial. The main page doesn't tell me what it costs.
- BusySync has a 30 day free trial. The main page tells me it costs $25
I distrust any vendor that hides their costs.
BusySync wins. I'll download their trial. If they fail, then I'll take another look at Spanning Sync.
Update: I gave BusySync an acid test -- and it failed. I reset a Google Calendar, then checked to see if BusySync would remove all the iCal appointments. It failed, instead I saw many ghosts. I'll give it another chance, but if they fail again I'll try Spanning Sync.
Update:
Ok, BusySync failed completely. On to Spanning Sync.No - it was Google Calendar Sync that failed that time. So BusySync only failed the removal test. So it's not out of consideration.