Woah, who knew NSIncrementalStore has been exactly what so many of us have been looking for. After a quick scan through, this looks like it completely replaces, not wraps, the default SQLLite store, yes? In other words, if the network is down, you can't save anything that would be synched later or request any queries that weren't cached? Or maybe I'm just not reading things right.

Full offline functionality is pretty important to us so I wonder if there is a nice way to make the NSIncrementalStore wrap a regular old SQLLite CoreData store and fault out to the network if something isn't found locally and conversely, store any new calls that need to be made until network is available.

As a long time Obj-C/iOS dev, web service interaction frameworks and/or best practices have been lacking for some time now. While RestKit works, it's learning curve is a tad steep and the sheer size of it can be a tad frightening in terms of 3rd party component reliance. If AFIncrementalStore is as great to work with as AFNetworking itself devs may have found themselves a new standard.