I made an iOS/Apple Watch app with WatchKit 1.0 that uses a shared group container and a custom framework to access the same Core Data store. Now, in the transition guide fo
I recommend setting up sync using the user info background transfer to mirror each database operation in both directions (if required) after transferring the store on first run.
The WWDC Session 713 - Introducing Watch Connectivity covers the mechanisms required. Nice API they've put together.
Yes, you'll have to maintain two separate stores. If either side is a "read-only" client and the CoreData datastore is small and changes infrequently you could potentially use the transferFile WatchConnectivity API to transfer the whole store each time it changes.