4 ms·
Wow, I've never read such a thorough review of a phone OS. So far the reviews have been surprisingly positive. I think it's not at iPhone 4 with this release,
by kenjackson 16y ago
Wow, I've never read such a thorough review of a phone OS. So far the reviews have been surprisingly positive. I think it's not at iPhone 4 with this release, but I think they came out very much in the hunt.
Here's what MS needs to do quickly:
1. They really need to hurry and get on Verizon and Sprint.
2. Add multitasking. They are going to get a lot more grief for not having it than the grief they'd get from some users who experience poorer battery life due to rogue background apps.
This one is really not that hard for them to do technically. If anything its probably just removing code paths where they fire events and shutdown processes.
3. Improve the Silverlight perf. 3rd party apps need to hum like 1st party apps.
4. Get IE9 out the door and the IE9 engine in the phone.
If they can deliver this early in 2011, then I think we'll see some sparks begin to fly.
- alnayyir 16y agoIt's a very nice looking OS, but there's no compelling reason for me to use it as opposed to my G2, or if I so desired, an iPhone so far as I can tell. The defaulting to Bing search and maps would in fact be a deal breaker for me. Non-existent tethering and linux support AFAIK too. Ugh.
- mjfern 16y agoIn addition to your points above, Microsoft needs to: 1. Make it easier for developers to port apps from iOS and Android to WP7. 2. Allow OEMs to customize WP7 and the hardware to some extent so they can effectively compete with differentiated and innovative products; else WP7 smartphones will become commoditized, just like Wintel PCs. 3. Consider a different revenue model. Charging $15 a copy to OEMs is a tall order, particularly when the competition is free (Android). Some have argued that the total costs of deploying and maintaining Android are higher than deploying WP7, but how can this be, given that almost all the costs with deploying Android are fixed in nature, while WP7 costs are primarily variable (on a per copy basis). 4. Improve its brand image in the smartphone market and across the board. Microsoft has a weak brand in the hacker community, given the preference for open source. Hackers are driving much of the innovation in the application markets.
- potatolicious 16y ago> "1. Make it easier for developers to port apps from iOS and Android to WP7." I disagree strongly with this point. The last thing they want to do is encourage developers to bring over UI paradigms from other platforms and just drop them into WP7. They've fought hard for a solid UI that reviewers seem to love (I like it too, having used one of the preprod phones) and it would all have been for nought if they cannot get 3rd parties to maintain consistency. That's one of Apple's strong points, and one of Android's problems - Apple devs give two shits about HCI, Android devs in general do not, and the average level of UI polish between the two platforms is phenomenally different. MS will have to go the Apple route if they want to compete, and this means being a bit draconian when it comes to HCI enforcement. Drop-in porting tools would compromise this. > "2. Allow OEMs to customize WP7 and the hardware to some extent so they can effectively compete with differentiated and innovative products; else WP7 smartphones will become commoditized, just like Wintel PCs." Oh Lord no. They've already compromised too much by allowing carrier crapware onto their phones. One thing Apple is good at is earning consumer trust - and part of that is doing things that act in their best interest (even if it means screwing developers). Their obsessive enforcement of HCI is indicative of this, and their complete refusal to bundle crapware is as well. You give OEMs the ability to customize WP7 and I guarantee that they will shit all over the gorgeous user experience that MS has obviously worked hard to create - and I guarantee that carriers will get right in this game also. > "4. Improve its brand image in the smartphone market and across the board. Microsoft has a weak brand in the hacker community, given the preference for open source. Hackers are driving much of the innovation in the application markets." I don't think it will matter. iOS is about as anti-hacker as a development platform gets, but it still has the support of the open source community. The fact that it's 'nix has a lot going for it (widely available libraries without too much porting effort), but in the end consumers will drive developers much moreso than the reverse. MS needs to drive a lot of customers to the platform, the developers will come after that, whether or not hackers actually like the company and platform is only a minor issue. If anything, I feel that MS should've gone for the Apple revenue model. One thing that both Google and MS have failed to grok, and one thing Apple has a very good idea of, is that the software and the hardware are inseparable. Designing the two separately is foolish and can only lead to compromising the user experience, and the market has shown in recent years that it weighs user experience far above that of raw functionality. You simply cannot create a halfway decent experience without knowing what hardware you are targeting. The case is worse in Android's case - since effectively the OEM is allowed to change the hardware spec in any way it chooses, leaving just about anything up in the air for devs to deal with. MS has obviously chosen a stricter model, but I fear it may not be strict enough.
- rimantas 16y ago1. Ok 2. I doubt it is that simple. Once you let apps to run in parallel you will need to manage them, to look after power consumption, have an UI to support multitasking, etc. 3. Ok, I guess that's easier than improve Flash for mobile. 4. I don't think the browser on WP7 is based on IE7 just for numbers to match. And this give me little hope there will be quick improvement in that area. Also there was this tidbit about detecting WP7 browser from user agent string. That's not the way to do it. The way to adapt your layout for a mobile device is using CSS media queries (IE9 should support those). BTW, about the interface. Some seem to really like it, but I find that clipped text a bit weird.
- borisk 16y ago>> 4. I don't think the browser on WP7 is based on IE7 just for numbers to match. And this give me little hope there will be quick improvement in that area. It is based on code from deskotop IE6 and 7: http://news.cnet.com/8301-13860_3-10452710-56.html http://news.cnet.com/8301-13860_3-10452710-56.html
- storm 16y agoIt's based on IE7, albeit with a few bits from IE8 sprinkled in (some JS and CSS selectors, I think).
- mattiask 16y agoI'm a little worried about point 3. I've done a fair amount of WPF (of which silverlight is a subset) programming on the desktop and while you can achieve pretty smooth animations they still arent as fluid as the ones we're seeing in iOS and built-in WP7 apps. The framework simply lacks some of the necessary support like V-Syncing to make that possible ATM. That's probably why native apps on WP7 aren't done in Silverlight and I'm not sure how they'll bridge that performance gap.