This means we don’t want customers to have to enter URLs, or set up accounts with third parties, or worry about router configurations. The second goal is that syncing should be easy to set up and effortless to use. And, as part of this setup, we don’t want to require that any device be on and running iBank except the one actually doing the current sync. (You can even sync two financial books on the same iPad, but I am not sure why you would want to.) Of course you can still include iBank for Mac in the mix. This means you can sync between iBank running on an iPad and an iPhone, or two (or more) iPhones, or two (or more) iPads, all without needing iBank for Mac. The first is to be able to sync any combination of supported devices without needing iBank for Mac to act as the hub. There were two key goals that have driven the design of our new sync solution. It became apparent that to get what we wanted, we were going to have to build it. We looked at working with DropBox or other host file storage systems, but again, these did not meet our needs. We looked at iCloud CoreData sync, but with the complexity of our model - including external file attachments and various schema differences between products - this option did not work for us. Since that time we have been researching various replacement solutions. We extended this model to support iPad and moved from MobileMe to webDAV when MobileMe was discontinued. It was designed with the Mac serving as a hub for all of the iPhones that sync with it.

Our current sync solution was originally designed to sync from iBank for Mac to iBank Mobile on the iPhone using MobileMe. Though it’s not ready for release just yet, I wanted to touch base with everyone to talk about how sync is shaping up.

It has been in development for some time now and is coming along nicely. Back in December, we announced we were working on a new sync solution for iBank.

Sync in evernote hack