Linked by Thom Holwerda on Fri 3rd May 2013 18:27 UTC
Windows "Microsoft's phone chief hates to call the new Nokia Lumia 521 cheap, but the lower-priced smartphone launching in the United States is the company's boldest move yet to win mass market share from leaders Apple and Samsung. The world's largest software company has so far focused on putting its Windows Phone software into expensive, high-end devices - chiefly from Nokia and HTC. But the new model will go on sale at Walmart later this month at an unsubsidized price under $150, relatively cheap for a new phone running up-to-date software without a long-term contract." Windows Phone is racing to the bottom just as fast as Android - with the difference being that expensive Android devices do not fail to sell.
Permalink for comment 560411
To read all comments associated with this story, please click here.
RE[3]: Forget it, it will fail.
by Nelson on Fri 3rd May 2013 21:26 UTC in reply to "RE[2]: Forget it, it will fail."
Nelson
Member since:
2005-11-29


The Android one is smarter by suggesting the special characters, web stuff, etc you need according to the situation, but other than that when you have to use multiple languages or more tech language, it' just doesn't complete those worst properly. Again, the BB10 keyboard is fantastic in comparison.


Windows Phone also does this with InputScopes, it just depends on the developer to tell the OS which type of input the text field requires. You can see this in the address bar in the browser vs a text box in the Messaging app. If this is what you mean.

I can probably see where it'd be limited in multiple languages and stuff, I wouldn't put it past MS to have a fantastic experience on select language. I really hate their geofenced approach to features.

It got better in 7.5 and 8, so hopefully the next set of updates improve the keyboard further. I think BB10 has done some fantastic work here, but hey, it is BlackBerry. If anyone's going to make a kickass keyboard it'll be them.


Still though, I think the problem I have is the fact that either the screen of the one I have is smaller than the bigger models, or the capacitive sensor is crappier, because I make much less mistakes on the Galaxy S.


Interesting. I used a Lumia 800 last year so I'm accustomed to the 3.7inch screen, but coming from my HD7 it was a definite learning curve.

When I got my 920 I had an adjustment period where I made more mistakes due to the time it takes my muscle memory to adapt. The 620's sensor may very well be of a lower quality, I've only had limited hands on time with the 620.

Resuming them takes a long time, but maybe because it's a 620 and it's slow?


Could be. By slow do you mean 1-3 seconds? More? Whenever I see "Resuming..." (Its only visible when you navigate *backwards* using the back button, since the app is rehydrating, and only if the app takes forever to restore its state) its only really been for maybe a second and it happens rarely.

I think it may come down to the fact that I install more or less big name apps, if you're giving the ecosystem a solid try and downloading apps from more questionable developers you might run into issues. There's a lot of gunk in the Windows Phone store, but there's also a lot of gems.

If you don't, I suggest an app called "AppFlow". Its an app discovery service which helps surface the gems on Windows Phone. You can also check the marketplace under "Collections" for some nice curated app selections too.



That makes more sense (though i fail to see why Nokia Maps and Skype, which are kind of first party fall into this category).


Me too. Especially for Nokia its surprising. I can confirm its a WP8 app that just doesn't opt in to the new behavior. At first I was in favor of the opt-in feature (especially after having to fix my own app when I enabled it) but now its clear that this needs to be be the default and affected apps should opt out.

An unrelated bit about WP7 apps:
Its easier to tell on a device with a 720p screen which apps are WP7 apps because they have letterboxing. On the 920 with a 768p screen, there is no letterboxing. On an 800x480 screen you won't ever notice unless it doesn't resume where it left off, or it starts up slowly.

WP7 apps aren't cloud compiled, so they're generally going to start a little slower.



Have you used Opera, Firefox or Chrome for Android? there's a sea of difference. Tabs are extremely cumbersome in WP8 IE, small links are harder to click/tap, and pages are not reloaded every time you go back to them (specially annoying when you are using 3G).


Yes, but quite some time ago. Chrome was still in Beta and still worse than the stock browser. Firefox had an odd UI and just seemed less polished. Opera I never did.


It's easy to tap links accidentally, which is made worse by the fact that if you go back a link and it doesn't even scroll the previous page to the point you were reading. It's just kind of immature in my opinion, which would be solved if Firefox or Opera were available for the platform.


I think that Microsoft should open the platform up to more browsers via some sort of 2nd party agreement. Consider the following: Some vendors during WP7's life time had authorization from Microsoft to use native code before it landed in the platform with WP8.

There's no reason why Microsoft can't white list Mozilla and Google's browsers if they show interest. I wish they would but the reasoning behind this are likely political. It just sucks because it'd make Microsoft faster to enhance IE.

I think the main problem here is that the core apps cant update independently of the OS. Why can't IE receive a marketplace update? or Email? or Calendar? They can on Windows 8 and it works great for out of band updates. WP8 needs to get here fast.

Reply Parent Score: 3