For the record, here is Google’s formal statement on the issue:
The mobile web version of Google Maps is optimized for WebKit browsers such as Chrome and Safari. However, since Internet Explorer is not a WebKit browser, Windows Phone devices are not able to access Google Maps for the mobile web.
The statement is somewhat odd. It would appear to be Google’s point that as Internet Explorer 10 for Windows Phone 8 uses a different rendering engine than what WebKit employs, it cannot process maps.google.com. This is perplexing as Internet Explorer 10 for Windows Phone 8 uses the same rendering engine as the desktop build of Internet Explorer 10, which is certainly capable of loading and running Google Maps.
Firefox, which is powered by Gecko and not WebKit, is also capable of rendering Google Maps. The mobile version of Mozilla’s browser does not, however, experience a redirect like Internet Explorer. We wonder what Google would say to this if Firefox was available for Windows Phone 8.
Furthermore, if you tell your Windows Phone 8 handset to render webpages in desktop mode, and head over to maps.google.co.uk, it should load. Google may redirect this link as well in the near future, so your mileage will vary. This contrasts with what TNW was told earlier; it was indicated to this publication that Google Maps had in fact never functioned on Windows Phone 8.
Our readers were quite upfront with their discomfort with this narrative:
“According to what TNW has learned, there has been no recent change leading to maps.google.com not functioning on Windows Phone 8 devices. This is as it has been”
As you can see in the video, that statement is rather inaccurate. What has changed is the redirect.
And:
Google is flat-out lying. They’ve modified their code to break Google Maps on Windows Phones. It worked before, but with the ‘redirect,’ it no longer works.