nokia – Terence Eden’s Blog

Ten Years Later - Was Elop Right?

@edent — Fri, 12 Feb 2021 12:25:17 +0000

A decade ago, Stephen Elop made the announcement that Nokia was adopting Windows Phone 7 as its platform of choice.

Being the mobile nerd that I was, I live Tweeted the press conference.

Let's take a look back to see what Elop and I got right or wrong.

Nokia killed off Meego - their new Linux platform. I was never that enamoured with it - but it could have had a promising future. The Balmer-led Microsoft was not as keen on Linux as the modern MS, so it's hard to see this as anything other than MS "disrupting" mainstream Linux adoption.

Windows Phone 7 didn't last. I was invited to review early version of the platform. And, while I liked the innovative UI, it wasn't close to its rivals at Apple or Google. It was obvious - to me at least - that Android was the superior platform and had the momentum behind it.

If you had a Mac, you could code for both Android and iOS (and others). But Microsoft's short-sighted decision to only allow development WP7 app development on Windows machines didn't encourage developers to code for WP7. You needed a Mac to make iPhone apps. Now MS expected you to buy a Windows laptop to code for their minority platform. That didn't fly.

As far as I recall, they didn't reveal any handsets. They basically told the market "Stop buying Nokia phones. Anything we release now will be unsupported shortly." That didn't encourage developers, customers, or retailers.

I got a Nokia Lumia to review in December that year. It was shit.

The Mobile World Congress show was the day after this announcement. If I remember correctly, the Nokia stand was weird that year. Dozens of phones which had no prospects. It did nothing to build hype in the platform.

There was no momentum. If they could have shown the secret phone that they'd been developing - and announced a launch date - it would have been a "wow" moment. Instead... nothing!

It is hard to launch a new device - especially in secret. But announcing a concept means nothing without something tangible to go with it.

Elop was right. Nokia would have been "just another" Android manufacturer. Instead, it became "just another WP7" manufacturer. I can see the arguments for both, but I would have loved to have seen a heavyweight Nokia as a counterbalance to Google.

And that's what happened. Why would HTC or Samsung or anyone make a WP7 phone if Nokia is Microsoft's preferred partner? Android was free and had fewer restrictions. Small companies like OnePlus would eventually find success with Android, in a way they could never have done with WP7.

I was wrong on this one! At the time, Blackberry was a surprising hit in the European youth market. Elop clearly didn't see them as a threat - and he was right. It was a dwindling platform with an uncertain future.

Blackberry - belatedly - jumped to Android. That wasn't enough to save them. It may not have been enough to save Nokia either.

Again, Elop was right on this. Nokia needed to continue its strategy of connecting people who had never been connected before. But splitting the company's focus between WP7 and "rest of market" wasn't a great plan. To be fair, Symbian probably wasn't the platform for that strategy either - but at least it had proven itself on low power devices. Something WP7 couldn't demonstrate.

Another page out of the MS playbook. And, to be fair, it probably kept Nokia going for a while. The mobile tech patent system was horrible (and probably still is). But did it encourage anyone to work with Nokia or MS? Or did it drive them to platforms with bigger pockets?

It was not. Nokia launched a fairly vanilla WP7 experience. There were a few Nokia touches - but they were crap:

Look, you can read the history of Nokia and see what happened to them. It was a brave an interesting choice to go with WP7. It would have been brilliant to have a three way ecosystem with iOS and Android. To be fair, WP7 could have been a contender. It had big corporate backing and was more future focussed than the ageing Symbian platform. The last few Symbian phones were awful - see my review of the N8. They were on a burning platform and needed to jump.

Could Meego have got anywhere? It was too encumbered by Nokia's desires and processes - it would never have been taken up in the same way Android was.

But, at the time, the smart money was on Android. Not just because Google were cool, but because WP7 had done nothing to disrupt the mobile market. They took the same 30% charge as other mobile platforms - so there was no financial incentive for devs. While Nokia has a huge marketing machine, Windows was a huge drag on the brand. Windows was something you were forced to use and regularly gave you a BSoD. If it had been the "Xbox Phone" that could have been something interesting - but it wasn't.

Was Elop an Microsoft plant sent to destroy Nokia? Probably not. But the board obviously thought that someone with strong links to MS was necessary to Nokia's future.

Nokia basically doesn't exist as a consumer handset brand any more in developed market. It is doing OK with basic phones in developing markets - but even there Android is the desired platform. Nokia is still successful on the radio and R&D - and perhaps that was the plan all along? Get out of the cut-throat handset business and sell big radio hardware to big mobile networks.

Either way, Elop's gamble didn't relaunch Nokia's handset business. And lots of people - including me - are still a bit sad about that.

Thirty Percent

@edent — Tue, 18 Aug 2020 11:30:01 +0000

A decade ago, I was invited to the UK launch of Windows Phone 7. It was Microsoft's attempt to compete with Apple's iPhone and Google's Android. Sure, Microsoft could make a brilliant OS and had excellent hardware partners - but could they convince developers to use yet another system?

At the time, I wrote:

The revenue share is 70/30. I really think MS have missed a trick here. It’s an “industry standard” price point because no one wants to get in to a price war. Increasing the share that goes to the developer would be an excellent way to convince wavering developers to adopt the platform.

Back in 2010, BlackBerry charged developers 30% as did Nokia Ovi, and HP's WebOS, app stores from Opera and Samsung charged the same amount, even the Amazon app store charged 30%. None have shifted their pricing in the last decade.

That's curious, isn't it? Surely a new entrant into the market - or one struggling to retain market share - would have picked a different revenue split?

What a coincidence that they all, independently, came to the conclusion that 30% was a fair and reasonable amount to charge developers.

In a healthy, competitive market, I would expect these companies to attempt to undercut each other. Sure, some of them offer incentives to large developers - and others offer promotions to smaller developers. But where's the price war to attract developers?

I doubt anyone has said "My favourite app is £1 cheaper on Android, time to ditch my iPhone and buy a Samsung!" But we know from the game console market that exclusive games drive purchases. Recently, Apple forced the removal of the popular "Dark Sky" app from Android - presumably because they wanted users to switch. Attracting developers and convincing them to concentrate on your platform doesn't rely on increased revenue share - but it sure can't hurt.

Obviously, I don't allege that they have acted as a cartel. I mean, just because Apple and Google colluded to suppress workers' wages, doesn't mean they've done so to suppress developers' income. A wide-ranging conspiracy to overcharge developers and pass those costs on to end-users seems unlikely. But I wonder why, in the last ten years, no one has challenged this seemingly arbitrary percentage.

And I wonder which app store will be the first to break ranks?

Symbian Won

@edent — Thu, 25 Jun 2020 11:44:49 +0000

I was working in the mobile phone industry just as smartphones were taking off. I saw the Palm Pilot rise and fall. I witnessed NEC and Sagem and a host of companies launch smartphones and then disappear. But the greatest tragedy of them all was Nokia and their Symbian Operating System.

(Actually, Symbian's ownership and relationship with Nokia is complex. But let's gloss over that for now.)

Symbian was, for its time, a brilliant OS. It ran 3D games smoothly, had terrific hardware support, a decent ecosystem for developers. And it was bloody annoying for users.

Every few minutes, Symbian would interrupt you to ask "Are you sure you want this app to connect to the Internet?"

"Are you super sure that you want it to connect to a secure site?"

"Would you like me to try to remember your choice?"

On and on it went. And then, with great fanfare, Apple and Google disrupted them.

Apple's model was "We have a curated store of artisanal apps, each one backed up by a legal entity with a DUNS number. We check them so you don't have to. Everything on our store is trustworthy."

Ha!

Google's model was "We'll tell you what kind of crap this app will use. Don't like it? Don't use it! YOLO!"

That, of course, led to ostensibly harmless apps asking for ridiculously invasive permissions.

Because, as it turns out, a Libertarian free-for-all doesn't work. It requires rational people to have an educated understanding of the risks they face. Millions of people installed dodgy apps, saw the one-time prompt, and lost control of their data.

With the latest releases of Android and iOS, we're back to where we started. Both now prompt you the first time an app asks for access. Both give you regular reminders of which apps may be snaffling your data. Both let you manage access and selectively deny apps.

There are many (many!) reasons why Symbian lost the Great Mobile Wars. But it is somehow fitting to see the return of design decisions they made decades ago.

Localisation is Hard - Nokia Here and Roundabouts

@edent — Thu, 13 Nov 2014 12:15:35 +0000

Last year I complained about a dangerous change to Google's Maps app. When driving, you want to spend the majority of your time concentrating on the road ahead. Flicking one's eyes to the mirrors & speedometer should be enough to quickly assess one's environment. The same applies for SatNav apps - every second that is spend trying to figure out what the graphics means is a second where the road goes unobserved.

Recently, I've been trying Nokia's new Here maps for Android. There's a lot to like about the app (more on that later) but it really doesn't handle British roundabouts particularly well.

Here are two screenshots I took of the same stretch of road. Nokia Here is on the left, Google Maps on the right.

At a glance, Nokia Maps tells me that I should be turning left. That's incorrect. The "2" icon - indicating the 2nd exit - has a higher cognitive load that a simple arrow. And anyone who has experienced the pleasure of Britain's roads knows that roundabouts often have sneaky exits which aren't immediately apparent.

Looking through the driving directions Nokia provides, it appears that all of its roundabout icons instruct the driver to turn left. I've scaled that image down so it should appear about the same size as you would see it on a smartphone. Can you make out the little notches and numbers?

Localisation doesn't just mean spelling "colour" correctly - it also means taking into account other cultural quirks like driving on the "wrong" side of the road, when to give way, and roundabouts.

That said, there are lots of things I do like about Nokia Here.

Cleaner interface. Google seems to think I need to know the name of every side street I pass, Nokia keeps it distraction free.
Speed limit - and current speed. In the UK it's fairly common to go from a 50MPH zone to 30MPH and back again in just a couple of metres (don't you just love our half-arsed metric conversion?!). In my observations, the Nokia app provided accurate speed limit information and, helpfully, played a sound over the car's Bluetooth speakers when the limit was being broken.
The traffic estimate in the bottom right corner is interesting. I'm not sure how useful it is to tell me how long I'll be stuck in a jam.
While I rarely use voice directions, I found Nokia's speech synthesis to be moderately clearer than Google's. There was also a wide variety of voices from which to choose.

On to the superior aspects of Google's navigation solutions.

The 3D depth offers a better view of the road ahead. While both apps will automatically zoom depending on speed, I felt like Google allowed me to see further.
Journey time. Both apps show the Estimated Time of Arrival (ETA) - which can be really useful. More often than not, I want to know how long until I get to my destination. With Nokia I have to glance at the small clock in the top right, then down to the bottom of the app, then perform some mental calculation in order to know that I've got 20 more minutes left. That's an increased mental load compared to the glance needed on Google.
Alternate routes. Again, both apps will helpfully suggest an alternate route should a faster journey time become apparent. Google places a button on screen which will quickly show all possible routes if you're sat in traffic.

Both apps work well. If Nokia could work out how roundabouts are supposed to work, the Here app would be a strong contender for my primary navigation app. As it is, I suspect many users will have grown used to Google's interface and - assuming they don't radically change it - will not want the added mental burden of trying use a new app while driving.

Lumia Review

@edent — Fri, 02 Dec 2011 09:52:44 +0000

It was the best of phones - it was the worst of phones...

I want to start this review by saying three things:

I got this phone for free - thanks Nokia!
I'm an extremely demanding mobile user. I recognise that I am an edge-case; what I find annoying, you may not.
I've tried to stick to actual bugs, not just "it does things differently."

Sergeant Elop's Lonely Phone Club

Imagine, of you will, you have just purchased a brand new copy of Sgt Pepper's Lonely Hearts Club Band on vinyl.

It is beautifully designed, an astonishing work of art. You play side one and it is sublime - perhaps the perfect start to any album.

The you flip the disc to side two - and it's Justin Bieber. A screeching, horrible, tune free noise that damages your calm and makes you want to smash your stereo.

That's the Lumia 800 from Nokia. It's Finland's first Windows Phone 7. It's beautiful and infuriating in equal measure.

The Good

There is much to praise the Lumia - and WP7 - for. So much potential - and nearly all of it squandered. But, we'll get to that... Let's start with what I love.

Beauty Is Skin Deep

The phone is gorgeous. Like a futuristic pop-tart. Sleek, shiny, and midnight black. It pulls off the incredible feat of being discreet and eye catching. A pure monoblock. As enigmatic and attractive as the monolith from 2001.

There's just one problem. We're in 2011.

A Brand New Operating System

Windows Phone 7 is different from all other phone operating systems before it. Sure, it has icons, widgets, lists, long presses, swipes, and ... you know what? It isn't different. It isn't a new paradigm. What it is, is gorgeous.

It's a sparse and elegant experience. Fast and user friendly.

The "Metro UI" is really easy to use, gentle on the eye, and a clever way to organise a phone.

Speed Demon

This is one of the fastest phones I've used. It's startup speed rivals that of BlackBerry. In day to day usage, I never found that it stuttered or slowed down - even while having several apps open at once.

Our Friends Connected

You can add in all your disparate social networks into your phone book. So, when you look up a contact, you can easily see their last status message, their Facebook photos etc.

Just like Vodafone 360 did years ago...

But, unlike 360, it works really well. It seemed to match up all my Twitter, Facebook, and address book friends without hassle.

Getting The Basics Right

Call quality was excellent. Good speaker phone. Fine reception. Basically, it works as a phone.

The camera is quick to focus and produces outstanding images.

Ok... ok... If you want to use it as a basic smartphone, the Lumia will do you fine. It browses the web, plays music, links all your social networks together, and looks beautiful while doing so.

It is basically fine - until you scratch beneath the surface.

The Bad

I thought that the Nokia N8 was the worst phone ever made by Nokia. The Lumia may come a close second.

I've been posting a running commentary on Twitter of all the niggles I have with the Lumia.

Here are the highlights - and slightly more in depth explanations - of every bug and annoyance I found. I have suffered, so that you may not.

Let's start off with a gentle one...

For a very modern operating system, WP7 has a fondness for outdated UI elements. I can't think of the last time I used a floppy disk.

That was the warm up. What would you say to a phone that you can't switch off?

I have since discovered that this only happens when the phone is plugged in. Maybe I'm unusual but, before going to bed, I switch off my phone and let it charge overnight. I've had several WP7 fans say that I should switch my phone on to flight mode (go in to settings, scroll through) or switch my phone on to silent if I don't want to be disturbed during the night.

There's just two problems with that. Firstly - why doesn't the phone tell me that I can't switch it off? Secondly - it's impossible to switch the phone on to silent.

Silence Is Golden

This may fall under the "just how I am used to it" school of errors, but bear me out. On every phone I've owned I've had three sound profiles that I can toggle through.

Ring and vibrate - what the phone is normally set to.
Vibrate - when I want to be notified, but having a loud ring isn't appropriate.
Silent - I don't want to be notified (I'm in a meeting).

With the Lumia, I can toggle between Ring+Vibrate and Vibrate. There's no way to get the phone to go silent without diving through a maze of menus.

In fairness, this is a problem which has affected recent Android phones - but there are multiple (free) widgets which solve it.

Screen Issues

The screen on the Lumia is a mixed bag. When it's displaying white text on a pure black background, it's perfect. When there's a white background, the screen seems - to me - to have lots of artefacts on it. The Lumia's screen is at its worst when dealing with greys, and solid blogs of colours. It suffers from lots of vertical banding which is really quite unpleasant.

I've scanned in the screen looking at a fairly normal grey image. While the scanner has overemphasised the problem (and my greasy finger prints!) you should be able to get an idea of how the problem manifests.

Browser Bugbears

Internet Explorer is a reasonable browser - but very buggy.

The URL bar keeps disappearing. I've had this a couple of times. The URL bar just vanishes when you're using the web. As far as I can tell, there's no way to bring it back.

The scrolling for the web browser sometimes stops responding.

Meeting You, Meeting Me

It's really hard to accept meeting invites on the Lumia. On my Exchange email, it works perfectly. For some Gmail invites, I have to click a link and go to Google Calendar on the web. The Lumia doesn't recognise .ics files - so there's no way the email client can talk to the calendar.

But, worse is to come. I asked someone at Microsoft to send me a meeting invite to my Gmail account. While the invite worked fine on the web, the Lumia gave me literally no way to answer the meeting invite - as this video demonstrates.

Crapware

This is Nokia's flagship phone - so you think they would have taken more care with it, wouldn't you? As well as a buggy OS, they've filled it with... let's just say "non-premium" apps.

Some apps, like this one from BA, need updating as soon as you switch on the phone. Sadly, you can't click a button to update - you have to go into the app store.

The greatest opprobrium is reserved for TripAdvisor. I know that deals like this take a lot of time and money to organise - but they really could have done better than this pathetic effort.

Still, at least they let you easily uninstall the bloat.

Things Go Better When We're Together

Microsoft may - or may not - be buying Nokia. One thing is for sure, they're working closely together. What's weird is why they've decided to duplicate some of the services on the phone.

I'm all for customer choice - but here, it just seems confusing.

Finally, Nokia seems to have its own app store. Once again, we see just how little Nokia care for UX.

Paperback Writer

The keyboard is a very strange beast. It's mostly fine, but has some oddities.

Weirdly, the word "Lumia" isn't in the Lumia's dictionary. So there's a little red squiggle ever time you write it. Or other common words.

That said - the in-line spell check is very nice. I miss it on my Android - I think I first saw it on the BlackBerry many years ago.

My Baby's Got Me Wrapped Up In Chains

We're living in a post-PC age. Unless you're Microsoft. You have to connect to a Windows PC to update software, copy across music and videos, change the BlueTooth name of the device, or even subscribe to podcasts.

What's worse, is you have to install the Zune software if you want to get music or photos off the device. You can't send via Bluetooth, you can't just shove in a USB cable and drag them off. You have to install the 100MB behemoth that is Zune, restart your PC several times, fire up the software, wait for it to detect your phone, then let it sync before you can get your photos out.

Of course, you could email your photos off the phone - but the UI for that is terrible. There's no way to select multiple images, so you have to attach each one individually.

It seems that any time you want to do something to your phone, you have to connect it to a PC running Windows.

Let's Talk About Text, Baby

Do you ever use read receipts for SMS? Perfect for seeing when someone has received your message. In every other phone on the planet, the read receipt is integrated in to the SMS app - so you can see at a glance which messages have been received.

With WP7, you get a long list of phone numbers which have received a message. It doesn't even do the simple task of showing you the name of your contact.

No Thanks

I hope that what I've shown you is a litany of bugs, errors, gotchas, and foul ups. I don't think any of the points I've raised are unfair. I like to think that I judge other phones just as harshly - see my treatment of BlackBerry and of iPhone and of Android.

I know this is a brand new OS - but you don't get credit for trying.

If you are prepared to stay in the walled garden, and put up with the bugs, the Lumia is a decent device. But there are devices which do more, cost less, and have more apps on them.

I'm not giving up on Windows Phone 7. It is still a work in progress. There is a great deal of potential here - and I look forward to seeing what the future brings.

For now though, avoid the Lumia. Wait until Microsoft fixes the bugs and until Nokia decides release a phone that they are happy with. Because, honestly, I don't think anyone at Nokia can believe this is the best that they can do.

Stephen Fry Ringtone

@edent — Tue, 29 Nov 2011 08:00:04 +0000

Stephen Fry has recently recorded a BBC podcast about the history of the mobile phone.

It's a really great series, and I encourage you to listen to it.

At one point in episode 4, Stephen sings the Nokia ringtone.

So, here it is for your edification, and delight.

🔊 Stephen Fry sings the Nokia Ringtone
🎤 edent

💾 Download this audio file.

Feel free to set it as your iPhone's ringtone :-)

All together now, "Derr-nerr-nerr-nerr Derr-nerr-nerr-nerr Derr-nerr-nerr-nerr Nerr!"

Dear Nokia...

@edent — Fri, 29 Apr 2011 10:53:08 +0000

Nokia's marketing team are idiots. They've used URL over which they have no control on an advert for one of their premium handsets.

This is the story of how I ~~hijacked~~ ~~stole~~ ~~hacked~~ recycled it and, in doing so, prevented Nokia from having a serious PR problem.

E7 Poster

This is advert for the new Nokia E7. It really emphasises the tweeting capabilities of the handset.

Nokia's marketing team have illustrated this by showing off a couple of tweets on the handset. One of which contains a Bit.ly short URL.

Here's the close up... it points to http://bit.ly/CYRWP

Being the curious chap that I am, I thought "Ooooh! I wonder where that'll take me? To some awesome Nokia competition page perhaps?"

So I typed it into my phone. Yup - the idiots in Nokia's marketing team didn't register the bit.ly link!

So, it was a simple matter for me to pop over to bit.ly, create a short URL pointing to this site, then customise it to say CYRWP.

Malicious Use

If I were a scallywag, I'd have pointed the URL to an Android website, or perhaps one of the less-than-stellar E7 reviews.

If I were nasty, I'd have pointed it to a malware page.

If I were a criminal genius (which I am not) I would have pointed it to a page which asked for credit-card number, email addresses, phone numbers, etc of people intetersted in buying / winning the handset.

I'm closer to scallywag than evil mastermind - so I pointed the URL to this blog post. Hopefully this page will serve as a reminder to Nokia's marketing team that you should....

Bootnote

Two other interesting things to note.

The #hashtag in the pictured tweet isn't hyperlinked. Tsk
The URL "CYRWP" is an anagram of "CRY WP". Are the Nokians in floods of tears over the death of Symbian and the coming rise of Windows Phone 7?

Augmented Reality Games - How Far Have We Come In 7 Years?

@edent — Sat, 06 Nov 2010 09:30:35 +0000

There's a delightful video doing the rounds of an Augmented Reality game for the iPhone. What better use of technology than to simulate the destruction of TIE Fighters?

While undoubtedly cool, what amuses me about this game is why it has taken the gaming world so long to catch up with Symbian! Way back in 2003, I got my hands on the Siemens SX1. It was the first non-Nokia handset to be running Symbian. As well as "modern" features like GPS, web browsing, and apps - it also came with a very interesting game.

Mozzies

Mozzies was an award winning Augmented Reality game. Perhaps the first of its kind to make it in to a mass market phone. I can't find any videos of it - so here are some screenshots. From a presentation by Andreas Jakl.

As you can see, not markedly different to the iPhone / Star Wars game. Sure, the graphics have come a long way - but it's still just tracking movement through the camera and accelerometer, and then painting shootable "baddies" on the screen.

Seven Year Itch

What annoys me about Symbian is that it has all these amazing and innovative features and then squanders them. I've never seen another Symbian handset with Mozzies on it. You'd think that an award winning game like that would be on every Symbian handset.

Another example. The N95 was technically superior to the original iPhone. Yet Nokia dragged its feet on using the camera accelerometer to power the screen rotation. Barely any updates came out for the the N95 series - any hope of using that as a platform to beat the onslaught on smartphones was wasted.

I don't know whether it's Symbian or Nokia or someone else who is to blame. What I do know is that Symbian has lost any technical lead it may have had. And that's desperately sad.

The Dark Side

In researching this blog post, I came across a delightfully disturbing tale of a young man who had his phone smashed for playing this game.

Heriyono said: 'I was so engrossed with the mosquitoes, I became oblivious to my surroundings.
'Then, I saw through the phone, a figure behind the swarm of mosquitoes heading in my direction but I thought he was just passing by.'
Heriyono claims the man then shouted: 'Trying to take a photo of my girlfriend, is it?'
And he smashed the phone on the floor.

I do wonder how many more phones will be destroyed when people think they are being used to take photos. Or how many photographers will use game playing as a cover?

Perhaps it's time to make a video app which merely looks like you're playing a game...?

N8 Fail - Reasons Why the Nokia N8 Sucks

@edent — Mon, 11 Oct 2010 08:16:39 +0000

Way back in 2010, I was sent a Nokia N8 to review. It was dreadful. Simply one of the worst devices I've ever used. My original ranty blog posts have been lost from tumblr, so I've reposted it here as a single post. It is pretty slapdash. I've added some commentary. Warning! There be swearing ahead!

On signing in to the N8, I was prompted to log in with my Ovi account. I have an account, but I can't remember the password. In order to retrieve it I must prove that I am human.

Oh, cool! A captcha when I try to recover my password. I’ll just type it in… Wait! What? I have to remember the captcha as well? Grrr….

Not only do I have to memorise it, I've got to try and type it in on a crappy T9 keypad! Why? Because the N8 doesn't support a portrait QWERTY keyboard!

One of the first things I do on a review phone is wipe it.

Considering how often you’ll need to resent the damn phone, this isn’t a very professional message. Why can’t the message box expand? Fckd if I knw.

This is a delightful usability fail.

https://shkspr.mobi/blog/wp-content/uploads/2010/10/N8-Usability-Fail-Small.mp4

Clicking “delete” pops up a box with a header and Yes/No buttons. Only the buttons are clickable.

Clicking on a link pops up a box with a header, a cancel button and a blank button. The header is clickable.

Consistent – kənˈsɪs tənt

I JUST WANT TO DISMISS THIS MEETING REMINDER!

https://shkspr.mobi/blog/wp-content/uploads/2010/10/N8-Dismiss-reminder-small.mp4

NOKIA - WHY DO YOU HATE ME?

The web browser is pretty crap.

Fuck No? Why would I ever want to use a secure connection on the Internet? Guess what? There’s no way to permanently remove this “helpful” message.

The misleading battery indicator was a nice touch.

There are only 5 bars showing. Mind you, there are only 7 bars in total. That’s nice and intuitive, isn’t it…?

The entire UI was a collection of bugs held together with bug juice.

A) WTF? There’s loads of space there?
B) What is going on in the background?
C) Android is quaking in its boots.

There were loads of weird help options hidden within the UI. Here are two of my favourites.

Just what’s needed to beat the iPhone. A “Breathing Light”. What. The. Juddering. Fuck?

Damn. And I was going to sell the N8 for scrap.

The UI was a weird mish-mash of "modern" touchscreen Symbian and "physical buttons" Symbian. Here's a particularly good example.

See that weird symbol on the Zero key? That launches the web browser. No! Seriously! It does! Because everyone starts to dial a phone number and then thinks “Damn, wish I could go to the web instead…”
Fun fact - 99% of people surveyed think that the icon resembles a phoenix rising from the ashes. It doesn’t.

Symbian was just full of legacy issues. Because of the N8's "unique" unibody design, you can’t open it. No user replaceable battery. No switching the phone off to change SIM card. Naturally, the OS hadn't been updated to reflect this.

Wait… What? Once I rip my fingers to shreds trying to open the rubber flap to get at the SIM card (no iPhone blessed paper-clip here) I have to restart the phone? Why? iPhone doesn’t do this. Android doesn’t do this. In fact…. no phone I’ve ever had asks you to restart the phone when you change SIM. What gives, Symbian?

The N8 does not have Ovi preinstalled!

When you go to the app store for the first time, you go to a website which then asks you to install Ovi.

This process takes ages. Well… 2 minutes. See for yourself in the video.

https://shkspr.mobi/blog/wp-content/uploads/2010/10/Nokia-Install-Ovi-Small.mp4

Why Nokia? Why? Why not just pre-install Ovi? Would it really be that hard for your teams to talk to each other?

Oh, and while you’re at it, sort out the install process. When the bar reaches the end - that means the install is done. It shouldn’t mean I have to scratch my ass for another few minutes.

While I’ve got your attention - why don’t those animated gifs rotate smoothly? What’s wwwwwwwwwith the judddddddddddddddddder?

FYI - here’s how it works on Android. Click on Market - Market launches.

Pretty much the same on iPhone and BlackBerry. You guys should totally buy one of your competitors’ devices. They have this thing called “out of the box experience”. It rocks.

Of course, once you install Ovi - it doesn't work properly.

My thought process…

1) Hey! There’s a WebTV icon taking up valuable screen space. I bet there’s something really amazing in there….

2) I… uh… oh… What? A single icon? No cool stuff for me? Why not just take me into Ovi rather than pushing another icon? Oh well… at least I’ve already installed Ovi. I can just click on the Ovi icon and go straight to the Ovi marketplace I already downloaded. Right?

3) Kill. Me. Now. Despite having already installed Ovi - this piece of stainless steel encrusted excrement has taken me to the web and wants me to download it again? Ah… no… it says I should download it again. But it automatically opens the Ovi store. I hope this is worth it.

4) This is literally the most depressing thing I’ve seen. Don’t get me wrong, I love me some Erotic Bollywood. I bet people from / in India are well chuffed to see India Today on there. What else is there? Hmmm… a 1 star rated “Gazzetta”. Something called “E!” which is apparently a utility. Or I can pay 4GBP for a cartoon.

No.

No. I simply don’t believe that this is what I am being offered. I refuse to believe that Nokia are this cack-handed. I’ve obviously got a defective unit with a defective Ovi store. That is literally the only explanation that makes sense. Who in their right mind at Nokia would have approved this? An icon that leads to another icon that leads to a web page that leads to a store with only 5 items in it?

Are Nokia playing a practical joke on me? IT’S NOT FUNNY GUYS!

This is the Nokia Ovi twitter client which is installed by default. It’s called social.

Notice the delightful light blue text on a light grey background. That’s SUPER EASY to read.

The client doesn’t support new style retweets either.

FFS. Shooting a video on the excellent 12MP camera. Can I play it back? Can I fuck.

https://shkspr.mobi/blog/wp-content/uploads/2010/10/N8-Play-Video-Small.mp4

I hope that my N8 is broken. I really do. That’s the only excuse I can think of. How hard is it to test these things?

It's not just me! My good friend RadioKate was practically in tears describing this horrible phone.

My original feedback to Nokia was "I actively resent using this device." It was true. The N8 was the nail in the coffin for Symbian. The N95 came out before the original iPhone and was hugely competitive for a non-touchscreen device. They saw the twin threat from Apple and Android and slapped a crappy touchscreen shim on their OS. It wasn't nearly enough. They pissed away their advantages until it was too late. The inadvisable switch to Windows Phone then killed the company. Shame.

Mobile Badvertising: Tesco, Nokia, Guardian

@edent — Sun, 19 Sep 2010 16:49:44 +0000

Three failures and one giant lost opportunity

Failure 1 - Targeting

This version of the Tesco shopping app is only available on Nokia phones. Nothing wrong with that - Nokia are still the biggest phone seller on the planet. So why allow the advert to be shown to Android users? It will annoy users, reduce your CPM, and make users less likely to click on adverts in future.

Failure 2 - Sizing

This is the full resolution on the advert.

(full resolution)

168*28 is barely enough to contain all the information you want to impart - let alone make it look attractive. The Tesco logo is tiny and indistinct - the wording blurred and hard to read.

Failure 3 - Mobile Friendly

Here we come to the failure that we see so often. A lack of mobile friendly landing page.

Responsibilities

Guardian needs to make sure its ad-server are only showing adverts relevant to the user viewing the site. The ad-server needs to make sure its adverts are scaled correctly for different phones. Tesco needs to ensure that its advertising agency is buying advertising space correctly. Nokia needs a mobile friendly page for non-Nokia devices.

Lost Opportunity

Just think what Nokia could be doing with this landing page for non-Nokia phones.

Show off the amazing capabilities of the app.
Display screenshots of the app.
Tell the user which phones the app works on.
"Don't have a Nokia? Take a look at these awesome devices!"
"Here's a map to your nearest Nokia store..."
"Get £100 off any Nokia device when you trade in your Android phone!"

You know the crazy thing? They do most of these things already!

If you try to download Ovi Maps on a non-Nokia - you get this page?

Nokia really need to have a joined up strategy for how they deal with users who have competitors' devices. Both the Guardian and Tesco need to do some quality control on their adverts and ad servers.

Mobile Badvertising: Nokia Music

@edent — Wed, 18 Aug 2010 16:52:50 +0000

I've mentioned Nokia on here a few times. For a mobile focused company, they seem to have a real problem with mobile advertising.

It starts well enough with an animated GIF.

The site it links to is music.nokia.co.uk/ - cleverly, Nokia redirect mobile users to a specific mobile version of the site. That's where it all starts to go wrong...

Viewport Is Your Friend

This is what the user sees on visiting the advert. Better hope they've got great eyesight!

This is caused by having an obnoxiously wide graphic at the top - but also by not setting the viewport correctly.

In the section of your HTML, you can define how wide the page should display. You can set the width of the page to automatically be that of the phone with this single line of code.

This will ensure your readers don't have to manually zoom in to read the marketing message you're trying to impart.

You can find more information about Viewport on Learn The Mobile Web.

Don't Link To Non-Mobile Sites

On this mobile website - where do you think the links lead?

Not only do they point to large pages totally unsuitable for mobile - one of the sites requires Flash to work. Thereby further excluding millions of potential customers.

It's one of the first rules of mobile advertising - don't force your customers to download megabytes of unusable data.

What Are You Trying To Do?

Finally, what's the point of this advertising campaign?

The main purpose seems to be to get me to download content on to my PC. An odd proposition for a mobile site, surely?

Given that it can't be used by anyone without a Nokia phone - why is it being served to me?

If it is trying to entice me to buy a Nokia device so I can experience "Comes With Music" - why is it doing its best to treat me like a second class citizen?

Ask yourself this question - what are Nokia trying to acheive with this advert. Nokia's effort doesn't seem to offer any value or information for anyone. What a waste of time and money.

EXCLUSIVE! Nokia Phones WILL Have Android!

@edent — Sat, 24 Jul 2010 09:34:33 +0000

Sauntering down Oxford Street, Mauricio Reyes spotted Nokia's secret Android plans.

Nokia phones "running" Android

Is this just a hapless Photoshop mistake - or a sign of things to come?!?!?!?! It's a daft graphic designer - obviously. But that doesn't mean we shouldn't take the possibility of Nokia devices running Android seriously. Oh, don't get me wrong, Nokia will never ship and Android powered phone - they've invested too much in Symbian and MeeGo for that. But Nokia devices will run Android.

A few years ago, I coaxed my Nokia N810 into running a prototype version of Android - NitDroid. The project has been resurrected by Stephen Hyde at NITDroid.com.

This latest video shows the Nokia N900 running Android's FroYo.

Why Is This Useful?

Nokia coined the term "Mobile Computer" for its range of phones. Computers aren't hermetically sealed consumer devices. They allow the customer to modify both hardware and software. You would be understandably upset if the computer you bought last year wouldn't let you install the latest version of Windows, MacOS, or Linux. But that's the situation mobile phone customers are faced with today.

The Android G1 has been abandoned by HTC and T-Mobile - much to the chagrin of customers. The HTC Hero has only been grudgingly updated to Android 2.1. Nokia left the N800 and N810 to rot. Nokia regularly stops development of its "mobile computer" software even when the devices are in active use.

Mobile phone manufacturers exist to sell phones. They don't get any extra revenue for releasing new firmware. Indeed, the cost of developing, testing, and shipping new firmware is prohibitively expensive. Not to mention dealing with customer complaints when things inevitably go wrong.

We are finally in a position to change that mindset. Hackers (in the original sense of the word) are now able to create custom firmware for new phones. Take a look at the XDA Developer Forums. Almost every Android phone released can have an improved firmware running on it.

True, a significantly older phone may not have hardware capable of running bleeding edge code - but it's enough to give it a new lease of life.

I'd love it if Nokia updated the N95 8GB firmware. The hardware is still incredibly capable.

In these tough economic times, it makes perfect sense to focus efforts on software, rather than hardware.

Look at the PS3 or the Xbox 360. A single model with firmware updates to increase its functionality.

Rather than tooling up a factory for a 6 month run of hardware - phone manufacturers should be looking to keep churning out a limited number of models of high spec phones for years. As manufacturing efficiencies improve, the hardware becomes cheaper and - like the PS3 and Xbox - cheaper models can be produced.

The PS3 came out in November 2006. Nearly 4 years ago. Can you think of a phone released four years ago which is still in production - let alone receiving firmware updates? The original iPhone was released in 2007 - it got a firmware update earlier this year but won't be receiving iOS4. Also, you can't buy a new iPhone 2G. Apple aren't in the business of selling inexpensive hardware.

The Future

I predict - or rather, I hope - we will see the following pattern emerge. Either from Google or Nokia.

An insanely expensive and over-spec'd phone will be released. I expect in the £500 - £1,000 range.
A public roadmap for its OS will be released - new features promised every 3-6 months.
A guarantee that official firmware development will continue for at least 3 years.
The OS will be sufficiently open to allow "homebrew" firmware to run. Hackers will jump at it.
The hardware will sell - poorly at first.
As production efficiencies are found, the price will come down. The hardware capabilities will stay compatible with older models.
The firmware will progress based upon consumer need, manufacturer desire and what hackers manage to achieve.
At around the 18 month mark, major new features in the firmware will be announced. This keeps the MNO happy as they don't have to subsidise the cost of new hardware for customers coming to the end of their contracts.
At the 2 year mark, the next hardware revision will be launched. More memory and megapixels - cheaper price.
If the hardware is still selling, expect others to follow.

The fly in the ointment for this is continuous manufacturer profitability. Apple, I understand, gets a cut of call and text revenue. Google gets a cut of apps sold. Microsoft and Sony sell licences for releasing games on their platform.

Would this "super phone" have to sell firmware updates? Would MNOs subsidise firmware rather than hardware? Would customers part-exchange an unfashionably old phone for the latest model?

Or will we be stuck with phones that are thrown on the scrap-heap by their creator in order to force us into buying the latest model?

One thing's for certain. Where there are hackers - there will always be updates.

Choosing a New Phone

@edent — Wed, 17 Mar 2010 14:05:15 +0000

ARRRRRGGGGHHHH!

Dead BlackBerry

Noooooooooooooooooooooooooooooooo!

Due to a crazy taxi driver (are there any other kind) and a violent swerve, my BlackBerry Bold 9000 is no more. Bereft of life, it rusts in pieces, and other such Pythonesque metaphors.

Arse. I truly feel like I'm missing an extension to my body. There's a symbiotic relationship which develops between a geek and his phone. It entertains me, informs me, keeps me on time and allows me to rapidly communicate with a variety of methods. In return, I feed it electricity, load it up with useful programs, decorate its skin and snuggle up to it.

I miss it so much.

Every Cloud...

Now's a prime time to choose a new smartphone. So many new models on the market. Which to go for?

What I look for in a mobile

I've had many many phones. Some wonderful (Treo 180) some dire (Apple iPhone). I know exactly what I want and what I need. For a device that I use several times an hour every single day, I don't want to compromise on any aspect. Perfection is what I demand. So, what was it that made the BlackBerry Bold the perfect phone for me?

Physical keyboard. I do a lot of typing on the device. I've used soft keyboards (Android, iPhone, Storm) and they just don't do it for me. Even with the haptic feedback, it's just not the same for speedy typing. I liked handwriting recognition on the Treo 180 and the Nokia N97 - but in terms of speed & accuracy a physical keyboard is a must. More than that, it needs to be a good keyboard. The keyboard on the N97 is dreadful - it feels like a cheap calculator. The N810 has an awful layout and virtually no travel on the button push. I need raised keys and to feel a click so I can touch-type.
Exchange integration. I use my device for work. Things which I regularly use my 'berry for are were: email and calendar sync'd over the air. Address lookup - if I meet Jo Blogs at work, I can type her name in to the address book and look up her email, phone number, address etc (if she's in the corporate address book).
The BlackBerry Enterprise messenger is also really useful. I don't use IM for personal use much any more - but work runs on it. Sadly it's basaed on Microsoft Office Communicator rather than anything open or useful.
Quick start-up. When you shut down a BlackBerry, it effectively goes into "suspend" mode. I switch it on first thing in the morning and it's on and receiving email instantly.
Auto on-off. At 2300 every weekday, my phone shuts down. So if I've forgotten to switch it off, I don't get disturbed during the night. At 0700 it wakes up and gets to work.
Multiple email accounts. I want to reply from 1 enterprise and 2 personal accounts.
USB interface for charging. Batter life isn't massivly important and I'm never away from a power socket for a few hours.
Compatible with Linux for charging, reading files, tethering.
Speed dial, form factor, excellent hierarchical bookmarks structure.
GPS & Mapping.
Good browser. I like the modern RIM browser - I know they're moving to Webkit, but I don't find the current one so bad.

Well, so far it looks like I'm going for a BlackBerry. Right. Not quite.

What I hate about BlackBerry

No front-facing-camera. I like video calling. I'm the only one in the UK who does, apparently. But with more 3G phones coming on to the market, I'm hopeful that more people will come round to it.
Lack of updates. It seems to take ages for any new developments to come out of RIM. I understand why - you can't fiddle around too much with business critical devices - but I like shiny new features.
Speed. Perhaps it's running OS 5.0 on the 9000, but everything seems a little sluggish. I'm very quick with my fingers yet I often feel like the 'berry isn't working as fast as I am. Once you're running IM, SocialScope, Facebook and Weather at the same time and everything slows to a crawl.
Camera. I like the flash and the geo-tagging, but the quality of images isn't wonderful. No focusing also impacts scanning QR codes.
Video recording - low quality and sound is often out of sync.
Calendar - only shows a single calendar. I don't want my personal appointments on my work calendar.
Media player. While it plays some .avi files better than Android, it won't do .ogg or .flac, the interface is sub par.

The Android Intervention

With my dearly departed long gone, I'm reliant on my Android device. An HTC Hero. It is a stunning device.

Gorgeous screen, very responsive.
Browser is good.
The camera is great although sorely lacking a flash.
It integrates with Microsoft Exchange reasonably well - although I haven't got it fully working yet.

But - and there's always a but...

HTC. They are very unresponsive to customer queries. No software updates for the Hero, even though they've been announced. Again, I understand the reasoning, but I don't want to be stuck on Android 2.1 when 3.9 is out.
Slow start up. I don't want to wait 60 seconds for my phone to wake up.
Lacking in functionality - although it has plenty of add on software, some at cost.
Lack of keyboard shortcuts. I rely on these heavily - as described in my comment to The Really Mobile Project.
Such tie in to the Google Eco-System. If I ever want to leave Google, I'm not sure how the phone would cope.

Others

I'm big on Linux. Despite the slight disappointment with Nokia's recent efforts, I'm intrigued by the N900. I think I'd like to play with it for a day - especially the keyboard given the disaster of the N810 - before comitting.

I've tried a 3G iPhone running OS3.0. It's a toy and really not suitable for me.

Windows Mobile is... lackluster. I can't wait for Windows Phone OS 7.0 Mobile (or whatever they're calling it today). Besides, I don't run Windows on my PCs - I can't think of a reason to run it on my phones.

What else is out there? Bada? Doubt Samsung call pull it off. Pre? I want to like Palm, but it's restricted to a single device and only on one network. Symbian? Hopefully it will be resurrected but after the disasterous N97 and the abandoned N95, it's dead to me.

Choices

I think it boils down to three phones.

BlackBerry 9700

Bold 9700

This is the "safe" choice. It's the next model up from my smashed 9000. I know it does everything I want. I like the idea of replacing the trackball with a touchpad. Good that it's got the new standard USB charger, even if I'll need to buy some new cables.

On the down side, it's a bit boring.

SonyEricson Experia X10 mini pro / Motorola Milestone / Droid

My Android choice. Has a keyboard and avoids HTC. I don't know how hackable it will be. Given it's one of SE's & Moto's first forays into Android, I'm concerned about how committed they'll be to the device.

Would really like an Android with a decent keyboard - there are just so few of them about.

Nokia N900

The outside choice. I generally love Nokia hardware - but their software sucks. As innovative as the N810 was, they really dropped the ball in providing updates to their original Maemo software. I'm slightly wary about how well this will be supported.

The keyboard looks ok, but the oddly placed space bar puts me off, as does the lack of ergonomic consideration.

Your Opinions

I'd love to know what you think. Which phones rock your world?

This blog is a personal comment and does not represent my employers, Vodafone Group. Nothing in this blog should be considered an official position on any phone, platform or manufacturer.

Mobile Badvertising - Nokia E72

@edent — Fri, 25 Dec 2009 13:56:06 +0000

Ahhh.... Nokia. Remember them? Once upon a time they were a global power-house. But now, with BlackBerry, iPhone and Android nipping at their heels, they are a shadow of their former self. I mean, Nokia "only" have a market share of 38% - and they "only" sold 108 million devices in the last quarter.... Hmmm.... Still - you know what will kick the arses of those American and Canadian rivals?

A Kick Arse Advertising Campaign!

That's pretty strong stuff. For those of you with poor eyesight, let's zoom in on the significant detail

Oh no they didn't!🔗

In the UK, I'm unused to seeing adverts which directly mention their competitors - let alone attack them. But in other parts of the world it's quite common. Personally, this sort of advert amuses me - but I do wonder how many people will find it childish and unbecoming of a global business. To say nothing of the fact that by mentioning your rival, you're giving them free publicity.

So, with a humdinger of an advert - this is bound to lead on to an awesome site. Probably with downloadable video showing how cool the handset is, maybe some lush product shots, at the very least the basic stats on these E72 bad boys. Right?

Wrong

Advert Destination

Oh. Is that it? It's just dumped me on the "Business Phones" page. A page which doesn't even work well on a mobile browser. Hey, Nokia, I know the BlackBerry's browser isn't the best in the world - but there's no need to rub it in! On top of that - there's no link to the E72. If I can be bothered to search for it, this is what I get.

Desktop E72 Page

Again, a non-mobile-friendly page which doesn't seem to say much.

It Doesn't Need To Be This Way

With a bit of judicious searching, I finally found my way to Nokia's mobile formatted E72 product page.

E72 Page

This is the page that the advert should have linked to. Yes, it's a bit dull. No, you can't buy the phone directly from here. But at least it goes directly to the product and focuses on its features.

It Really Doesn't Need To Be This Way

As good as that page is, there are some obvious failing. No product shots, no comparison with BlackBerry (the main thrust of the original advert), no links to buy the product.

The daft thing is, Nokia has some wonderfully designed mobile-friendly product pages.

Nokia's 5800 Page

They even - get this - have phone numbers so you can order one of their products. It's hardly a revolutionary idea - let your customers give you money - but it's totally absent from the first advert.

Call Me

There are a whole mish-mash of different visual styles on offer.

N900 Page

It's probably enough to give Nokia's branding team a coronary - but there's no denying that these pages are visually interesting, and offer much more information in a much more engaging way than the E72 page.

N97 Page

Conclusion

Where to start...?

Make sure your MOBILE advert links through to a MOBILE FRIENDLY page.
If you're a mobile phone company - this is doubly true.
Follow up on your advert's promise. If you say "This product is better than Brand X" - show that.
Make a visually appealing site. This WWW medium isn't paper. You're not charged extra for printing in colour.
Let your customers buy your product. Sounds simple, doesn't it? Add a phone number or an email address on there if they can't buy directly with their phone.
Provide as much information about your product as you can. This is your chance to wow your customer. Plain text and small images just won't cut it. Again, you're not being charged per printed page - so go nuts. If you can, offer some video content.
Finally, and this is a biggie, link directly to your products page. If I've clicked on an advert for a Gizmo XYZ, don't take me to Gizmo Corp's front page - take me directly to what I've said I want to see.

These are really basic points - yet we see big companies fail to deliver again and again. Mobile advertising is big business, but you wouldn't know it from looking at this advert.

Nokia Ovi - 25 Mistakes

@edent — Tue, 26 May 2009 14:14:15 +0000

I know a thing or two about mobile websites. The last 4 years of my life have been spent obsessing over them. I wouldn't claim that the sites I run are the best in the world - but I've picked up a thing or two about how a successful mobile retail channel should work. Nokia's Ovi gets everything wrong. I'm going to show you 25 easily avoidable mistakes in the new Ovi Store.

Here's how to make a successful downloads platform:

Make it easy for your customers to buy things.
...er....
Nope. That's pretty much it.

So, here's the front page of the Ovi Store.

Count the errors

Here's every error I can find on the above the fold page...

Incomplete titles. "Star Trek Noki"? Surely "Nokia"? Looks sloppy and unprofessional.
Poor descriptions. "Ringtones In Cinemas Now!"? Ringtones aren't in cinemas. Is that one ringtone or several I'll be downloading? If you don't tell me what it is I'm getting, why would I download it?
Ratings. Why would you put unrated (or rated zero) content at the front of the store? You want your killer apps there.
Search. Why do I need to click through to search? There should be a text field and button there, not a link.
Colour differentiation. Using white and then light grey doesn't help customers easily scan across the page. A darker shade would help.
Menu bar. Is there an order to it? Is there a reason it splits haphazardly over three lines? The longer the menu - the less space for content. As it is, it's a pretty poor use of space.
No Nokia branding. I know they're trying to promote Ovi as a brand - but no one knows about it yet. The use of the Nokia logo would really help customers trust the store.

...and breathe...

Let's assume we're reckless enough to click on "Star Trek Noki". What do we find?

Oh dear...

Let's take this from the top. Don't forget, this is the Nokia Ovi Store's FIRST link. This is what they really want you to buy.

Where's the description? What exactly am I buying? It turns out, this is the product placement tune in the new Star Trek film. Some descriptive text would help. I thought it was going to be the film's theme tune!
The description - such as it is - appears half way down the page. Why do I have to scroll to see what I'm getting?
Photos? Why do I need photos of a ringtone? Why are there "more" photos when there's only the one?
The product photo is, essentially, black. A bit of colour to liven up the page wouldn't hurt.
The review - why isn't it in English?
Are the related links Games, Videos, Ringtones? Some context would help.

I clicked on download and got a blank page. Once I refreshed the page, the download started.

Huh?

Files should be named. It makes it easier for the user to find in their filesystem, it looks more professional when downloading.

So, I play the file and what do I get

Real professional lookin'

Add some fracking ID3 tags! It makes it easier for the user, it looks more professional and it costs the supplier nothing!

Gah! Fine. Ok. I'll go back to the store and grab something else. I click back and am presented with this monstrosity.

Where do we go from here?

Nothing. Not even a page telling me how to get back. How is this meant to encourage me to buy more? This page should thank me for downloading. It should encourage me to buy more. In this case, I'd expect to see more Star Trek merchandise that Nokia want to sell to me.

Contrast this with the N-Gage download from the N-Gage site.

Much better

Once my download is completed, I get sent back to a nice page which lets me continue enjoying the store. Nokia have this technology for Ovi - but not in the Ovi Store. Bizarre.

Last, but not least - registration. I know that Nokia has to have a registration process - they don't have an MNO's advantage of seeing a customer's phone number. They also don't have an associated account which they can reuse - like Google or Apple.

Oh... No... Wait... They do. I've registered for a Nokia account, an Ovi account and a Mosh account. I don't seem to be able to use any of them with Ovi Store. NIH syndrome?

To be fair, the sign up process isn't too bad. Apple could learn a lot from it.

A pretty good sign up screen

The only criticisms I have are the "Mobile Number" field should be masked so the user can only enter numbers. I also think that a captcha is a bit of an overkill on a mobile site.

Good to see that the example number is from Ofcom's reserved range.

Overall, this is a step backwards for Nokia. Mosh and the original Ovi were quite good. This is just a mess. By my count, there are at least 25 basic mistakes just from going to the front page and downloading a ringtone.

25 mistakes in 3 clicks.

[Disclaimer. In the interests of fairness, I work for Vodafone. Specifically looking after Vodafone live! a direct competitor to Ovi. The thoughts expressed in this post are my own and not those of my employer. I have nothing against Nokia; I kick up as much of a fuss about Apple and BlackBerry too!]

Nokia Ovi Store. Oh dear...

@edent — Tue, 26 May 2009 09:49:43 +0000

I try so hard to like Nokia. Their hardware is second to none - but when it comes to software and services, they haven't got a clue.

They've just announced a new app store - Ovi Store. This is to replace the broken mess that is Mosh, N-Gage, Download and the current Ovi. Why do I get the feeling that there are several fiefdoms within Nokia all working against one and other rather than working together?

So, let's take a look at the new service.

Nokia Ovi Store - Wow!

Wow... just wow. A blank page. Not even a "coming soon" message. Lest you think I'm using some kind of shonky phone, I'm on a Nokia N95 8GB, firmware 20.0.016, in rather good HSDPA coverage.

You're supposed to be able to get to Ovi via the "Download!" application. I don't think I've used "Download!" since I first got the phone. On the surface it's a nice little App Store. If Nokia given it some love and attention, it would have got the recognition it deserved as the first integrated app store. As it is, it was left to die.

...please wait...

After 5 minutes of waiting for the "Download!" store to finish "Processing" I got bored. After 15 minutes nothing more had happened so I tried to cancel. Turns out you can't, so I rebooted the phone.

Never mind! I'll try going through the regular Ovi site.

Can you spot the store link?

No link to their brand new store. Hmmm.... odd.... Maybe I have to sign in to see it. Yes, that sounds plausible.

This isn't looking good...

Ok, a dodgy certificate isn't the worst error in the world. It's one of those things that says "We haven't tested our site and we really don't care if scary error messages put off our customers."

In any case, the sign in service doesn't work.

Ovi Error

Ah... Well, let's try again...

It just gets better and better

Right. So the site has no links and it doesn't work. Perhaps I imagined the Ovi Store launch? Let's check the Internet Oracle that is Google...

There's something there...

Google has found it! It must be there. Ok, so there's still a dodgy certificate - but I can't wait to start spending money with Nokia! Here we go!

Oh. Just another blank page.

So, there you have it, folks. The word "FAIL!" is overused, I feel. How about we agree to replace it with "NOKIA!"?

Nitdroid: Installing Android on the Nokia N810

@edent — Sun, 03 May 2009 07:41:00 +0000

I'm continually frustrated with Nokia. They make truly excellent hardware but always seem to produce the most disappointing software. The N95 & the N810 are perfect examples of this. Powerful and innovative computers let down by shoddy software.

So, when I heard that some clever hackers had ported Google's Android OS to the N810, I leapt at the chance to reinvigorate my sadly neglected Internet Tablet..

There are various tutorials on the web, but here's my quick & pain free howto for people running Ubuntu. This is based on the instructions from the Nitdroid Homepage and the InternetTabletTalk forums.

You will need...

A Nokia N810 (this should also work with the N800 and the N770)
USB and Charging cables.
A computer running Ubuntu (or most other flavours of Linux)
A working Internet connection.
NERVES OF STEEL! (Not really, it's very simple to reflash the N810 if you do mess up.)

So here's the HOWTO:

Back up any files you want to keep from your N810. We're going to be wiping it clean.
Remove any SD cards you've got from the N810.
Make sure the battery is fully charged.
Create a folder on your computer called "Nitdroid".
Download the following files (or newer if available)
The flasher - this allows you to flash the hardware (you may need a different version if you're running 64bit or PPC).
The Android filesystem
The Android OS
Connect your N810 to your computer via USB, switch the N810 on.
If you haven't got it already, install and run gparted.
You need to create 3 partitions, the first must be FAT32, the third must be ext3 with a minimum size of 128MB. See the picture for an example.
Take a note of the device name - in this example, it's /dev/sdb
We need to mount the ext3 filesystem we've created - go to the command line and type
sudo mount -t ext3 /dev/sdb3 /android
Remember to change /dev/sdb3 to whatever your device is actually called.
We now need to go to the "/android" directory and extract the filesystem to it. At the command line, type
cd /android

Then
sudo tar -xjpvf /home/$USER/Desktop/nitdroid/rootfs-nitdroid.tar.bz
Remember to change $USER to your username - or change the whole path to where you downloaded the nitdroid files.
Once complete, you unmount the filesystem by typing
sudo umount /android
We're ready to flash! Hurrah!
Turn off the N810, unplug it from the power and USB cables.
We need to make the flashing software executable so type
chmod a+x flasher-3.0-static
Plug the N810 into the USB cable but leave it switched off.
Run the flashing software (yes, with the N810 turned off) by typing
sudo ./flasher-3.0-static -f -k zImage-nitdroid-n8x0 --enable-rd-mode -R
You will see the following message
flasher v0.9.0 (Jan 19 2007)
Suitable USB device not found, waiting
This means that the flashing software is looking for the N810.
On the N810, hold down the "Switch" button (The one which looks like two overlapping squares, just under the camera). With the button held down, push the power button.
You'll see some messages on your PC's screen indicating that the device is being flashed. Let go of the buttons.
Wait.
Wait a little while longer.
Have a biscuit to calm your nerves.
It should be over and done with in less than a minute.
Once it's complete, unplug the N810. Power it off, then on again. You should see this screen.
It takes about 5 minutes for the first boot to complete. If it takes substantially longer than that, read the troubleshooting section.
TADA! You now have Android on your N810.WiFi works - as do the keyboard and touchscreen. At the moment, sound, BlueTooth & GPS don't. There are a few random crashes, and the performance leaves a little to be desired. Much like the original Maemo software!

Troubleshooting.
If it all goes wrong, here's how to get your N810 back to the latest official firmware.

Download the latest official firmware from http://tablets-dev.nokia.com/nokia_N810.php
Plug the N810 into the USB cable but leave it switched off.
Run the flashing software (yes, with the N810 turned off) by typing
sudo ./flasher-3.0 -F RX-44_DIABLO_5.2008.43-7_PR_COMBINED_MR0_ARM.bin -f -R
Remember to replace "RX-44...." with the name of the latest software.
You will see the following message
flasher v0.9.0 (Jan 19 2007)
Suitable USB device not found, waiting
This means that the flashing software is looking for the N810.
On the N810, hold down the "Switch" button (The one which looks like two overlapping squares, just under the camera). With the button held down, push the power button.
Wait. You will have a factory fresh N810 in a matter of minutes.

Enjoy!

N-gage user experience. 100% failure.

@edent — Fri, 04 Apr 2008 09:34:00 +0000

I really want to like Nokia. They produce some amazing hardware, but time and time again, they're let down by poor software with a dreadful user experience.

Take the recent n-gage launch. N-gage was a flop when it originally launched several years ago. It's absolutely critical for Nokia to get this relaunch right or else they face a T5 like PR failure.

But Nokia being Nokia, they've fallen at the first hurdle...

I'm going to take you through the process that a brand new user has to go through to get the software.

First failure, The user has to click the n-gage icon that has lain dormant on their phone since its purchase. Nokia has no "push" marketing to users - they expect the user to visit them. That's assuming that the user hasn't already deleted the n-gage app from their phone.

So, the user clicks on the app and goes to update the software.

Second failure No automatic redirection to download the app, not even a clickable link. Please try and remember his URL and type it into your phone's browser.

Third failure So, you type in the URL and get this... What's the point of this screen? I'm here to get content, not read your blog.

Fourth failure What phone do I have? You tell me! Use automatic device detection so people don't have to remember the obscure model number you've given the phone.

Fifth failure So, you start downloading and wait and wait

The download comes in at a whopping 7MB! There's no indication on the site that it's such a weighty download. The UI doesn't tell you how big it is and how long it will take. 7MB takes an age to download - even on HSDPA - and if you're on a pay per MB deal, you won't be happy watching the download going on and on and on.

Five failures. Five barriers to entry before a customer even gets to pay Nokia for their games.

Come on Nokia, you must do better.

Turn Your N95 into an iPhone

@edent — Mon, 17 Dec 2007 11:32:00 +0000

Samir has just released this little auto-rotate app for the N95. As you rotate your phone, the screen reorients itself. It's a brilliant idea and an excellent application... But it really calls into question Nokia's ability to react to the market.

The N95 has always had an accelerometer (the device which tells it which way up it is) but it has only ever been used to stablise photos. What a waste!

The N95 was released in March 2007 whereas the iPhone was released a few months later in June. However, the iPhone's rotating screen was known well in advance of release. With several firmware updates for the N95, it's shocking that it takes a 3rd party developer to release such a compelling UI upgrade.

The N95 8GB is also missing this functionality - despite being released as an "iPhone killer". The new Channels service from Nokia Beta Labs has auto-rotate built in - but still no word on whether a future firmware upgrade will include a native rotate function.

I'm not a big fan of the iPhone - but I hope it lights a fire underneath the other manufacturers and gets them to raise their game.

Turn your N95 into a Light Sabre

@edent — Fri, 16 Nov 2007 16:18:00 +0000

Use your N95 to slice iPhones in half.
Light Sabre for the N95

It's uses the N95's built in accelerometer. Expect your office to erupt with geekish joy as soon as the first "hmmmmmm" begins.