That company is Facebook.
Facebook doesn't have a very good history with Windows Phone, refusing the commit an official app for the platform till today, forcing Microsoft to come up with its own (arguably not very good) version of the Facebook app.
Throughout the life of WP, users were forced to endure the WAP version of Facebook Mobile, as the touch-optimized site is buggy most of the time.
However, I noticed significant improvements since the release of WP8 (which the improvements can even be felt on WP7 devices). They cleaned up a lot of the quirks and made touch.facebook.com more usable to WP users. In fact, touch.facebook.com is highly usable for WP users today, with very few things not working.
As of a few hours ago, the (new) bug of not being able to touch on specific friend requests/messages/notifications have been fixed.
Going back, more improvements and fixes were made. One major one is the ability to side-scroll (go to your Timeline and try it out). Previously, all side-scrolls on the web are done through WebKit specific method, now Facebook uses a more universal approach. Some other improvements are: able to see entire pictures finally (switch to landscape to make the picture bigger), layout of like/comment on posts are fixed, sidebar functional and many more.
Obviously, there are many more improvements to be made.(I still can't go to a person's profile by tapping on the tagged link on a photo, for instance.) The same can be said of Microsoft's mobile web browser, which is still lacking compared to the competition. But the point is, Facebook is progressing and improving its services to more users, while Google decides to alienate more users.
The future of mobile web in terms of support for IE still seems uncertain. Many basic mobile webs work just fine, but requiring anything just a little bit more complex such as side-scrolling then support for IE Mobile just seems nonexistent. (For example, m.gsmarena.com uses WebKit specific code for side-scrolling) Go for more complicated web apps such as Google Maps, then you start to see why Google couldn't be bothered to provide any sort of usable experience in the first place, as everything is so entrenched in WebKit.
TL,DR: Even with small number of users, Facebook decides to increase support for WP while Google decides to entirely alienate and scale back support. Go try touch.facebook.com.
Facebook doesn't have a very good history with Windows Phone, refusing the commit an official app for the platform till today, forcing Microsoft to come up with its own (arguably not very good) version of the Facebook app.
Throughout the life of WP, users were forced to endure the WAP version of Facebook Mobile, as the touch-optimized site is buggy most of the time.
However, I noticed significant improvements since the release of WP8 (which the improvements can even be felt on WP7 devices). They cleaned up a lot of the quirks and made touch.facebook.com more usable to WP users. In fact, touch.facebook.com is highly usable for WP users today, with very few things not working.
As of a few hours ago, the (new) bug of not being able to touch on specific friend requests/messages/notifications have been fixed.
Going back, more improvements and fixes were made. One major one is the ability to side-scroll (go to your Timeline and try it out). Previously, all side-scrolls on the web are done through WebKit specific method, now Facebook uses a more universal approach. Some other improvements are: able to see entire pictures finally (switch to landscape to make the picture bigger), layout of like/comment on posts are fixed, sidebar functional and many more.
Obviously, there are many more improvements to be made.(I still can't go to a person's profile by tapping on the tagged link on a photo, for instance.) The same can be said of Microsoft's mobile web browser, which is still lacking compared to the competition. But the point is, Facebook is progressing and improving its services to more users, while Google decides to alienate more users.
The future of mobile web in terms of support for IE still seems uncertain. Many basic mobile webs work just fine, but requiring anything just a little bit more complex such as side-scrolling then support for IE Mobile just seems nonexistent. (For example, m.gsmarena.com uses WebKit specific code for side-scrolling) Go for more complicated web apps such as Google Maps, then you start to see why Google couldn't be bothered to provide any sort of usable experience in the first place, as everything is so entrenched in WebKit.
TL,DR: Even with small number of users, Facebook decides to increase support for WP while Google decides to entirely alienate and scale back support. Go try touch.facebook.com.