Thursday, February 12, 2009
Tuesday, February 10, 2009
The mysterious 'squares' in contact names problem has also been fixed, along with a few contact issues seen with Windows Mobile devices (file-as not being always set, contacts appearing as 'Unknown').
Monday, February 9, 2009
Here are some answers to the questions we've been asked today:
Is Google's new sync service similar to Nuevasync ? Yes the two services use the same sync capabilities present in the same devices including the iPhone, and today provide a similar set of features.
Did Google use any of our technology? No.
Does this mean the end of Nuevasync ? No, there will be much more to Nuevasync than today's Google sync service.
Is this good news for Nuevasync ? Yes. I'm pleased that Google have adopted our approach to mobile sync. It's also good to read that they are using their resources and influence with device vendors to enhance the quality of device sync client code.
If you guys weren't planning to become the sync engine for Google, why did you create your Google service ? We wanted to develop really solid sync server software and Google was picked as a data source back in 2007 when work began on our 'demo' service. Google had a decent calendar application and a usable API. The plan was to attract a few hundred users and fix any bugs they revealed in the code. There are 120,000 users today so we over-achieved a little on the plan but we've also fixed some very obscure bugs!
Which new features are coming next ? E-mail sync (from any IMAP mailbox), support for other calendar services besides Google, a solution for users who need to use a corporate Exchange server, tasks support, major web site improvements. We will also fix all the bugs ;) Keep the support mails coming...