I was hired to build something like Ensembles[0] for an Apple Design-award winning iOS/Mac software developer in 2009 (and did) that needed seamless Core Data s

I was hired to build something like Ensembles[0] for an Apple Design-award winning iOS/Mac software developer in 2009 (and did) that needed seamless Core Data sync across a suite of iOS and Mac OS X apps. At the time, I considered building a startup around the technology, but in the end decided not to because I believed the market was too small. It's been interesting watching the development of Core Data sync, and at least at this point, feel I made the right decision. Sync is an interesting problem, but you can nearly always build a specialized solution when you need to for your specific data model that is _much_ simpler than the "general" case, and that handles conflicts better. Given how long Ensembles has been available (over two years), how much the developer charges for a commercial license (peanuts), and the fact that it's basically a "lifestyle" business for him, I think it's clear that there's not much of a market for object graph sync. [0] http://www.ensembles.io/ http://www.ensembles.io/