Linked by Thom Holwerda on Sat 5th Jan 2013 14:53 UTC
Talk, Rumors, X Versus Y And so this situation is starting to get ridiculous - and consumers are, as usual, caught in the middle of it all. Google has just blocked Windows Phone devices from accessing Google Maps on their phones. In addition, it also seems Windows Phone users are now restricted to the basic HTML version of the mobile GMail website. While understandable from a defensive perspective - Microsoft's extortion scheme targeting Android device makers and all that - it's still a massive dick move that only hurts consumers. Update: the media attention has worked - Google is backpedalling, and will remove the redirect. "We periodically test Google Maps compatibility with mobile browsers to make sure we deliver the best experience for those users. In our last test, IE mobile still did not offer a good maps experience with no ability to pan or zoom and perform basic map functionality. As a result, we chose to continue to redirect IE mobile users to where they could at least make local searches. The Firefox mobile browser did offer a somewhat better user experience and that’s why there is no redirect for those users. Recent improvements to IE mobile and Google Maps now deliver a better experience and we are currently working to remove the redirect. We will continue to test Google Maps compatibility with other mobile browsers to ensure the best possible experience for users."
Thread beginning with comment 547607
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[5]: Comment by shmerl
by shmerl on Sun 6th Jan 2013 22:51 UTC in reply to "RE[4]: Comment by shmerl"
Member since:

Google also went against their own promise to drop H.264 support from Chrome. (They never promised to drop Flash though). Not keeping their own words is worse. However dropping H.264 from the browser wouldn't be enough to promote open codec. They had to ditch it from YouTube to make a real push. But probably because of slow adoption of accelerated VP8 hardware decoding, they decided not to. I hope they'll do it when more chip makers will support VP8 out of the box.

Edited 2013-01-06 22:52 UTC

Reply Parent Score: 2