Windows Phone might be easier to use for a beginner. Why? It uses lots of button and we people are used to use buttons. On keyboards, on non-smartphones etc, etc… That doesn’t mean that swipe-UI would be less intuitive – we’re just not used to it, but that is because we’re influence by what we already know.

F.e at the good old windows times you had to click “start/shut-down” to turn your system off. That’s not intuitive at all. But I remember when I worked with a friend on a Mac-Computer a while a go and he was wondering where the Start-button is to shut the computer down. Ridiculous right? But that’s how we’re influenced…

Other example; many people were so used to use non-QWERTY (numberpad) that it felt wrong to write text messages with a QWERTY keyboard which was f.e on the iPhone standard – today every smartphone has only this option (exception might by Symbian) and nobody looks back to numberpad-typing.

And a last example, very off-topic though; The plane manufacturer Airbus produced years ago the first airliner which was controlled through a a little joystick. Most pilots say that you have to get used to it first, because its not like the typical paddle airlines have. But many of those pilots love that joystick once they’re used to it and even if it’s hard to adapt first – those joysticks are very intuitive.

Now think again about the comparison of those two Nokia-phones…
To me, Meego is very intuitive and once you use it, you don’t wanna go back to anything else. But it’s a fact that this system is still very young and if you’re just a simple phone user, you could have some problems to set everything up. Some things are just not 100% finished in the Meego System.

We can buy phones w/o fear of certain core hw features being left out. Simply because we opted to buy outright, instead of on contract.
It often works out to be way better value too.

Cheers.

Yes I’m aware of that issue.
It’s got nothing to do with the hand-over process, despite appearing that way.

But it’s well doco’d & apparently a fix is already in place for 1.2.
Apparently it was due for 1.1, but didn’t quite make the cut in time.

The OS was effectively started from scratch about last Oct.
They’ve done pretty well considering.
Esp. since the team’s been downsized a bit since Feb, when if anything it needed to up-sized.
Hopefully the stock browser won’t be quite as sparse in 1.2.
That is the feature release.

No I brushed off as rant the prior paragraph, which did make no sense.
I honestly had no issue getting it going right away.
And I’m no ubergeek…