Google is making a nice gesture today by extending the cutoff point for using EAS (Exchange Active Sync) to sync Google services to Windows Phone devices until July 31, 2013. If you'll recall back to December 2012, Google swiftly pulled support for EAS on Windows Phones, with the service set to expire today, January 30th. Google's hope was to move everyone over to using IMAP -- along with CalDAV and CardDAV for contacts and calendar -- to sync all types of devices. Because Android and iOS both support IMAP, CalDAV and CardDAV there were no issues to be had. Windows Phone, on the other hand, didn't have the extra protocols ready to go and was about to leave new customers out in the cold when they went to add Google accounts to their devices.
Luckily for both Microsoft and its customers, the new deal extends EAS support for Google Account syncing another 6 months. This will give Microsoft time to properly integrate CalDAV and CardDAV into Windows Phone, so that when this new extended cutoff period ends users will not be losing any features.
Source: Official Windows Phone Blog; More: WPCentral
Andrew was an Executive Editor, U.S. at Android Central between 2012 and 2020.
Good for Google and Microsoft. Glad cooler heads prevailed here and both didn't resort to screwing their users out of spite.
Google is chilling with Microsoft because BB10 has been announced for less than a day, and Google already knows who the new 3rd OS is. Sorry "Micro", you're just "soft" now.
"Google's hope was to move everyone over to using IMAP -- along with CalDAV and CardDAV for contacts and calendar -- to sync all types of devices." Then why was it only for Gmail accounts, while Google Apps were not affected?
This also applies to Windows 8 too, I believe!
This doesn't alter the fact that this is a spiteful move by Google. Customers of both companies are the real losers.
so when is android central renaming itself to google central?
Get the best of Android Central in in your inbox, every day!
Thank you for signing up to Android Central. You will receive a verification email shortly.
There was a problem. Please refresh the page and try again.