Ember and iCloud Core Data
One of the biggest challenges we faced last year with Ember was sync. Once you start using Ember, it’s incredibly easy to build up a substantial library - and customers upgrading from LittleSnapper have sometimes many thousands more images imported! Multi-gigabyte libraries are not uncommon, and combined with (in particular) iCloud customers have found sync to be problematic. It especially doesn’t help that iCloud is a very hard-to-inspect black box, and there’s no progress shown to you as to the uploaded (or not) state of your library. It’s tough to say it, as iCloud’s robustness has continued to improve each year, but right now iCloud isn‘t a good fit for apps like Ember, and our future product direction will reflect that.
Last year they were optimistic that iCloud Core Data would improve. Now—three plus years after iCloud Core Data shipped—it sounds like they are giving up on it.
5 Comments RSS · Twitter
Crap, the linked post has already gone into link rot oblivion, and I don't have an archive of it.
"Crap, the linked post has already gone into link rot oblivion, and I don't have an archive of it."
Here, let me Wayback Machine that for you...
(Please make yourself aware of all internet traditions, charles.)
Thanks, Chucky! Should have thought of it.
The Ember guys told me on twitter they're working on fixing that too.
[…] or not: Ember and iCloud Core Data – “Now—three plus years after iCloud Core Data shipped—it sounds like they are […]
[…] Previously: Ember and iCloud Core Data. […]