|
|
|
|
|
by freehunter
5280 days ago
|
|
The UX must be consistently slick
This point is useless, the entire number 4 in your post. First of all, if you're using it as a point, you've never used a Windows Phone. It's as stable as an iPhone (certainly moreso than Android), I've had one since April and have never had a crash, lockup, or misplaced UI element. You seem to be bringing that from Windows Mobile, which is hands down the biggest thing holding Windows Phone back right now. Technical people who cannot and will not distinguish between it and its unrelated predecessor.This argument pisses me off because it's completely unfounded, yet I constantly hear people saying "Well, I have my doubts since it's a Microsoft product" without ever using it. The biggest hurdle to Windows Phone 7 is ignorant techies casting misinformation to the general consumer just because bashing Microsoft is a fun talking point. |
|
I have read that there are issues with proper implementation and understanding of UI conventions with WP7. Certainly, this is true for the iPhone as well: not all iPhone apps are consistent or slick, and the UI conventions have some key differences from desktop apps. It will be even more critical for WP7, since they have a markedly different set of UI conventions.
Given that the developer pool for WP7 is much smaller at this point, a few highly visible but poorly implemented apps are going to have a disproportionate effect. That would be a pity, as Metro really is a setup up in UX design from iPhone.