Nokia Lumia 920 First Impressions

So, after eagerly awaiting the Nokia event in New York for the last couple of weeks it's finally all over.

I currently use a Nokia Lumia 800, I love the Windows Phone 7.5 OS (although I'm painfully aware of some of it's limitations), and was hoping to see a raft of features on offer that would have me taking a hammer to the piggy bank.

The hammer, I'm sad to say, is staying in the garage for a while.

The Lumia 920 is indeed an excellent looking phone, and from as much as we've been told ticks most, if not all, of the boxes for me. Except one.

Whilst Windows Phone 8 (re)introduces support for SD cards, and there is an MicroSD card slot on the mid-range Lumia 820, this is sadly lacking on the 920.

Why?

Don't get me wrong, the 32Gb of on-board memory is quite good, but I fear on a phone that I hope to keep using for at least two years this will get filled up pretty quickly.

I've had the Lumia 800 since early this year and I'm already at the stage where purchased applications take up the lions share of internal memory, leaving me limited space for music and movies. I regularly see a "not enough space" message when updating the libraries for the following day. This is a situation I can only see getting worse with the new applications that will begin to appear.

Sure, the Lumia 920 features double the memory of my Lumia 800, but it's still not enough, especially considering that the new screen is begging to be used to view movies.

So 32Gb of memory will lead to compromises, whilst 32Gb with a MicroSD slot and a card of 64Gb (or possibly higher in the future?) giving 96Gb of space would lead to... well, fewer compromises (yes I really do have that much music, and it's not always possible/practical to stream music).

So the Lumia 920 is still in the running, especially if the Nokia software bundle is as strong as it has been on the current models, but this one seemingly simple omission has got me considering alternatives. It's not the no-brainer I was hoping it would be.

I wonder how that Samsung Ativ S will turn out...

I wonder how this will pan out...

Well, I don't think Microsoft will be loosing much sleep over it, but it appears that two unrelated situations mean I'm going to start looking into developing Android applications rather than for Windows Phone, at least in the short term, allow me to explain:

The first culprits involve the decisions Microsoft are taking with the direction of Windows Phone 7. It started off with the removal (or is it actually more accurate to say omission?) of Cut and Paste functionality. From articles I've been reading recently this is down to a lack of time for getting it developed by release time, rather than not knowing how to implement it. As a friend from Nokia commented "What, were they worried they could do cut and not paste in the time available?".

The lack of C&P was originally sold to developers as a conscious decision ("A phone doesn't need C&P" - Really? Then why write Office Tools for it?), now we're told "it's coming later". Not the end of the world, but frustrating. Still, I agree it's better to get it right than put in something that's buggy or badly designed and then be stuck with it forever more.

The killer move, for me, is the apparent lack of any way of side-loading applications. As is the case with iOS, you get your applications from Windows Marketplace or not at all. That's essentially shut me out. It's all very well running anything I code in a desktop emulator, but then I may as well have just written a desktop application. If I can't actually get it onto a phone (and possibly those of my friends) what's the point? This is the number one reason why I've avoided Apple phones all this time.

Then there is the work related chain of events.

When I started out at my previous job the plan was to move into C# (as I believed the role required, it's certainly what was advertised and what I interviewed for). Previously I had been working in Java but I was happy to move to C#, it's a great langusge. Being a Java developer a large personal application I had been working on I was also written in Java. When I "moved" to C# I started porting my code over too. Doing such things works as a good aid in getting to grips with a new language or language features.

Now I'm going back the other way to Java as the primary language in my work role, so guess what else I'm now planning on doing? [Moving my application back to Java]

Here's the killer: Just as I was hoping the C# code would allow me to share core components of the application between Windows, Windows Mobile and Phone, and possibly web sites, it turns out that the primary development language for Android appears to be Java.

So now Java potentially gives me access to Android Phones, The Android OS (for Laptops, Slates, etc.), and with a little work (hopefully not too much) Windows, Linux, MacOS, possibly even MeeGo. Oh, and I believe web servers can also run something called servlets too. Oh, and just for fun, the Windows Mobile phone I currently have includes Java too... oh, and I know S60 used to run Java. Wow!

The killer which I'm brushing over is obviously that there will be an incredible amount of work to customise the user experience and display for each system, possibly this could be the lions share of the work, but I do at least take some comfort that at least some of the core business logic may be sharable between systems.

Looks like until my priorities change again this is the logical route for me to get back into Java in my spare time above the demands of work.

So now the new laptop has arrived one of the first things going onto it will be a shiny new install of Eclipse and the Android SDK. Oh, did I mention that's all free? That's possibly a little unfair a comparison, the Express versions of Visual Studio are excellent (that's one of the downsides to all this, I find the Visual Studio IDE an absolute joy to use. For Java development I prefer NetBeans, but since I'm on Eclipse at work, and most of the Android documentation references Eclipse I may as well use that).

Will you ever see any of these fruits of my labour? probably not (almost certainly not), but the point is the more I play, the more I learn, and as long as some of that is relevant I end up getting something out of it over and above the hobby side.

Now, of course, I'm reliant on Oracle not screwing things up with Java (well, no more than Sun managed at the very least).

Fingers crossed.

Willing to drift?

As if the love-in for Apple devices at BP isn't enough, I recently watched a guy on my train home using his iPad as an eBook reader. This got me thinking "I could be tempted by an Android slate" (see earlier posts for why iOS and Windows Phone devices are not on my radar).

The is remarkable for me as only a few months ago I would not have entertained this thought at all, in fact I was only interested in running Windows 7 on a tablet. I have to admit my ideal device would still be this, but the swish iPad equivalent hardware for PC devices is, I fear, still some time away.

I loved my tablet, but it was too bulky, too underpowered and the screen was too dim/fuzzy due to the touch functionality. However. technology moves on and now all of these issues have now been solved, but strangely not in one device.

Touchscreens are now much clearer and more vibrant. The mobile versions of the Core chips and similar offerings from AMD are very capable. Laptops, whilst not as light as an iPad also weigh much less now. And the deal maker or breaker for my next purchase will be battery life (I had too many occasions with my last tablet where it died half way through a journey home).

I had whittled my choice down to either an HP tm2 tablet, basically an updated version of my current (very sickly) tablet, or an Acer 5820 with an almost 7 hour battery life and Core i5. Out of the two the Acer is a more powerful machine, but lacks the touchscreen, if only they had included this I'd have had the credit card out last week instead of still plucking up the courage to part with my cash.

And that's my point; why is it so hard to put a touchscreen on a decently specified machine? I know it's going to add to the price, weight, and you have to design in the hinge, etc., but it's surely not that difficult is it? Who is going to be the first company to step up to the mark? It's a problem that's been commented on for an age, and now just seems to be accepted: "It you want a tablet or slate you must sacrifice power and other features". Why?

So it seems I'm going to be stumping up for a regular laptop this time, safe in the knowledge that my ideal tablet won't arrive at least until it's time to upgrade again, possibly after this (Did I hear Windows 8?).

So what about the Android slate? Well the reality is I have no neeed for a slate device so it's just a "perhaps one day" thought. An iPad may have appealed if it supported flash and wasn't locked into the app store.

What really strikes me, as I mentioned before, is how I am now even considering an Android device over Windows (be afraid Microsoft, you're starting to loose the faithful like me). But at the same time I take comfort in the fact that I am able to see beyond the brand, and it mirrors what's happening on my desktop too.

Sure I've experimented with Linux over the years from Red Hat to Ubuntu, but for all its sins Windows has suited me far better (yes, even Vista). Linux has always had an air of "not quite" about it, not for everyone, but for my "needs" and probably "wants".

18 months ago I went mental when somebody installed Chrome on my mums PC. I was running mostly Firefox and a little IE7 when required. When IE8 arrived I found it better for my liking than Firefox (which had started to show signs of copying the worst problems of IE) so switched back to mostly IE8. Now I find I'm increasingly using a combination of Chrome and IE8, especially after reading the results from a recent security conference where all the other main browsers were hacked in around 10 minutes, yet for the second year running chrome resisted attack.

On the Java IDE front I used to be a massive fan of JBuilder. This was eventually replaced by Eclipse in my toolbox, then Netbeans, and now, mostly from necessity, I find myself back to Eclipse again. It's just a case of the right tool, or the necessary tool for the job.

As I get older I'm having less of an emotional tie to software and devices, and more of a practical attachment, which is why I don't need to be locked in any more than is necessary. Of course, this is not possible as any software I do buy, unless it is free and available on multiple platforms, will inherently be tied to a platform(s).

That's one of the reasons why things like Adobe Flash, Java and to a (much) lesser extent Silverlight and .Net are important as they facilitate some level of platform drift. And that's the real reason why Apple doesn't want you to have them.

The rumor for Windows 8 is that it too will have an application marketplace. The way Microsoft seem to be mimicking Apple these days, I fear the day when you can only run approved applications in Windows may not be far off. When that happens perhaps it won't just be Google's Chrome that's on my desktop.

Damn you HTC...?

I've always been quite keen on keeping the firmware of my phones up to date, so as soon as a new ROM image is made available I tend to install it at the earliest possible opportunity. This doesn't tend to happen very often, and is made worse when the phone is operator locked, however you can normally count on three or four updates during the first couple of years as long as the phone remains a current model.

My old Nokia N95 was locked to T-Mobile, so many updates never appeared, and those that did usually appeared several months after the generic roms had been released into the wild. This time around, my HTC Touch Pro2 is a geneneric unlocked device, so I'm at the top of the list when it comes to ROM updates.

The TP2 was supplied with Windows Mobile 6.1, and soon after the 6.5 upgrade was released I updated to this. Everything was working very well and the phone was very stable, 6.5 looked fairly impressive. A few months after this another new ROM image was released containing a some bug fixes from Microsoft and an update by HTC to a later Sense UI featuring closer integration to FaceBook and a built in Twitter client, so I duly updated to this - and that's when my troubles started.

I suspected the new Sense UI was ported from the version written for the HD2 or similar recent Windows phone, as the whole responsiveness has became considerably slower than the original WinMo 6.5 Sense UI. I can't help thinking it was therefore aimed at the newer, faster devices, and just slung onto older models with few, if any, modifications.

The first thing I noticed was updating contacts linked to FaceBook. At first I though this just crashed, in actual fact it's taking several hours (even over a Wi-Fi connection) to update the few contacts (sub 20) I have linked to their FaceBook profiles. That's not really acceptable

The bigger problem I've encountered is a couple of times when making a call. What happens is I'll select my contact from the list, and the phone will report it's calling them... until a different contact from my list answers. When you hang up the phone history list correctly states you called the wrong number.

This is simply not acceptable.

Along with this, the phone has become very unstable, locking for minutes at a time or crashing altogether on a frequent basis, I've even missed a couple of calls due to this (and been unable to terminate calls on several occasions ). I can also forget about using the speaker-phone (although that may be yet another hardware fault).

As mentioned I suspected this wasn't so much down to the underlying OS as much as Sense itself. To prove this I turned the Sense UI off and for the first time tried to use the new Windows Mobile 6.5 UI instead. It's not as good, but I figured that if it works it will be bearable until they hopefully release another ROM update.

I'm now a few days in and whilst there's several things about Sense I am missing, the actual 6.5 UI isn't too terrible. Interestingly, I'm not yet sure if things have been made any better on the reliability front. The phone does now boot several seconds faster (as it no longer needs to load Sense), but I have had at least a couple of occasions where it has frozen for several seconds, so if it is better now, it's not by much at the moment (Apple fans please don't tell me this wouldn't happen on an iPhone, I know several iPhone users who regularly curse the reliability of the device, one even has to reboot his phone every time he travels from London City to Docklands for some bizarre reason. This isn't just an issue with Windows Mobile).

I'll probably try a hard reset at some point but since these problems started soon after a bare update, I'm not hopeful. I'll be sure to let you know how I get on.

Of course, the downside of all of this is that I'm now a little wary of getting another HTC phone. I was thinking of a Nexus 2 if that's out by the time my contract comes up for renewal in December. We'll have to see now, mind you if it is down to the underlying OS, I'm unfairly giving HTC the blame. Mind you, I don't suppose Android is flawless...

Windows Phone 7 Burning The Boats

Joey deVilla has written an interesting article on the Global Nerdy blog: Apple, Windows Phone 7 and Burning the Boats (or: Why I Think Windows Phone 7 Doesn’t Have Copy and Paste)

It’s a thought, and I see the point, but the fact still remains that I want a phone that will let me do what Windows Mobile allows, so again I’ll re-iterate that I’m probably not the (initial) target market for the new phone. That’s a shame.

In semi-related news, I’ve been playing with Android 2.1 on my HTC Touch Pro2 to get a feel for it. So far the jury is out, but I haven’t given it a fair amount of time, it is, after all, a whole new OS to get to grips with and, for the moment at least, I am literally stabbing around willing things to work. Time will tell, but once I’m used to it (if I get that far) it will gain “likely points” on the “What new phone” decision that will take place at some point.

WPF Phone

I can already hear the iPhone owners: "Windows Phone 7 UI is a copy of the iPhone UI". I will understand this, but it's only looking at the UI from the perspective of an iPhone user.

I've not used an iPhone, primarily because I know that however good the OS looks (and it does look good), it doesn't offer the features I want (neither does Windows Phone 7, as mentioned many times before). However I was just browsing through a few screenshots of apps on the iTunes web pages and one thing repeatedly kept hitting me: "These apps look like they were written in WPF!"

WPF has been around since (AFAICR) the release of Vista, and at that time, as far as I was aware, Microsoft weren't trying to ape the iPhone UI to the desktop (although I dare say some inspiration was drawn from there, as is the nature with these things, although reading some of the documentation and tutorials on WPF I would say they were after a version of HTML for creating Windows clients originally).

WPF is the brother to Silverlight (with the alleged intention apparently to end up with a single technology at some point)

And  of course Windows Phone 7 is based on Silverlight and XNA.

I can see where this is going...

On an aside, several years ago there were hot rumours of Microsoft going into competition with the Sony PSP and Nintendo DS. I can't think of any device they are scheduled to launch in the fall that may be doing this...

It's been argued before, but finally I can see mobile killing the likes of the PSP and DS. Perhaps it's a shame NGage never caught on after all.

Smart Phones

I recently upgraded my phone to an HTC Touch Pro2 which runs Windows Phone (supplied with 6.1 but now running the free 6.5 ROM update), and it’s a purchase I’m extremely pleased with, despite having to send it back to get the space bar on the keyboard and the speakerphone microphone fixed. The true test of how good I think it is is the answer to the question “Would I buy another?”, which would have to be an almost definite “Yes!”. The almost part being that I’d possibly got for the new HTC HD2, which has better hardware (although no physical keyboard, but still runs Windows Phone OS.

But here’s the thing: I never recommend phones running Windows to anyone other than other developers.

Why?

Well, I chose a phone running this OS as I actually like it. It’s not the fact that, despite there only being a few apps on the Windows Marketplace there are actually more Window CE applications than for any other device (yes, including the iPhone and possibly even Symbian devices).

I don’t mind that many of the applications are designed with a stylus in mind, I had an iPaq back in 2004 and have used that ever since, so it’s actually an input method I am comfortable with. Actually, I think having a device entirely finger driven is not something I’m looking for, having the phone functionality covered by fingers is fine for me, and HTCs Sense interface they overlay on their phones (including their impressive range of Android phones) goes further than I need in achieving this.

I also have a few paid for apps from my iPaq which still run without problems.

The camera isn’t all that good, but I knew that before I bought the device, and is hardly a consequence of the OS.

One of the main reasons for getting a Windows Phone is that I can write software for it using C#, a language I’m using in the workplace. I’ve already knocked up a couple of small applications and found it remarkably easy.

But the point is most people don’t want to use the phone in the same way I do, hence why I will usually recommend either an Android base smart phone, or an iPhone.

I’d never touch an iPhone myself, but that’s because it doesn’t offer me the things I want from a phone, and I think the way apple treats their customers and developers stinks. That’s all I’m going to say on the matter at the moment. What I will say is that the virus known as iTunes does a good job of managing the purchase of Apples chosen applications, and is simple enough for my less technical friends to use. And I suppose I should mention there’s a lot of good games for it.

Shame the phone functionality itself is a little…. sub-optimal.

My favourite alternative at the moment is many of the Android based phones. I really think this is the OS to watch, and if they can break the Apple love fest (which is a very difficult nut to crack) then this is the phone with the best prospects.

Then, of course, there’s Symbian, who ship more licences than any of the others (possibly combined). I had a Nokia N95 and was generally happy with it, but it was a bit buggy. Through talking to a friend who worked at Symbian he convinced me that this was probably down to what Nokia had ‘added’ to the OS, but the net result is the same.

So please don’t tell my your iPhone is better than my Windows Phone as I won’t listen. Yes, it’s probably a better phone for you, but not for me. Enjoy playing with your iBeer, and leave me alone, I’ll be busy writing OneNote documents and Excel spreadsheets on a device that’s donig what I want it to, and a lot more besides.

(BTW: I deleted the Windows Phone version of iBeer, it was OK, but what’s the point.)