Skip to main content

Mpx-220, no thanks!

Finally got my hands on the Motorola Mpx-220 Windows Mobile Smartphone and was well...massively unimpressed.

I'm a fan of clamshell phones, they are usually smaller and the screen has better protection from scratching etc. I plumped for my SPV e200 back in the summer as A) it was a free upgrade and B) the Mpx-200 was only Windows Mobile 2002 - no .NET CF support.

So after running with a candybar phone for about 6 months now I was keen to see how a clamshell felt again and how it stacked up against the awesome
c500, the latest SPV offering from Orange.

Initial impressions of the 220 are that it's an ugly phone..big ugly phone. I liked the 200 design and you can see
here how much bigger the 220 is from the previous version. The 220 design is very fussy and the bit where the aerial is makes it look like a shaver IMHO! (now there's another great idea...mobile with built in shaver!).

The nails in the coffin were the small screen and the build quality - the battery cover is fairly loose fit and rattles - not really a problem, you could pad it out or something but the general impression when the phone is in your hand is that it feels cheap. It looks and feels like a phone from 2 years ago...

Ok it has some serious specs and a great camera but the sort of photos I take with my phone are really few and far between and the VGA cameras you get now are easily adequate for fun photos. Right now if you are in the market for a Windows Smartphone there is only one solution - the c500, incredibly small, light and very well built...good battery life and brilliant screen.

Look out for the SPV3i - a variant with a central joystick control like the e200 rather than the weird bar control.


Comments

I like the weird control bar - I don't understand why everyone else has such a problem with it?

C500 is my first non Nokia, and it's great.

Popular posts from this blog

Walk-Thru: Using Wolfpack to automatically deploy and smoke test your system

First, some history... The advent of NuGet has revolutionised many many aspects of the .Net ecosystem; MyGet, Chocolatey & OctopusDeploy to name a few solutions building upon its success bring even more features to the table. I also spotted that NuGet could solve a problem I was having with my OSS System Monitoring software Wolfpack ; essentially this is a core application framework that uses plugins for extension ( Wolfpack Contrib ) but how to unify, standardise and streamline how these plugins are made available? NuGet to the rescue again - I wrapped the NuGet infrastructure (I deem NuGet to be so ubiquitous and stable that is has transcended into the software "infrastrucuture" hall of fame) with a new OSS project called Sidewinder . Sidewinder allows me to wrap all my little extension and plugins in NuGet packages and deploy them directly from the Wolfpack application - it even allows me to issue a new version of Wolfpack and have Wolfpack update itself, sweet huh

Configuration in .Net 2.0

11-Dec-2007 Update I've updated this post to fix the broken images and replaced them with inline text for the example xml and accompanying C# code. This post has been by far the most hit on this blog and along with the comments about the missing images I thought it was time to update it! Whilst recreating the examples below I zipped up the working source code and xml file and loaded this onto my Project Distributor site - please download it to get a full working custom configuration to play with! Just click on the CustomConfigExampleSource link on the right hand side, then the "Source" link to get the zip. We are in the process of converting our codebase to .Net 2.0. We've used Enterprise Library to great effect so decided that we should continue with this in the form of the Jan 2006 release which targets 2.0 and I've got the job of porting our Logging, Data Access etc wrappers to EntLib 2.0. ...And so far so good - the EntLib docs aren't bad and the migrati

Castle/Windsor schema enables Visual Studio intellisense

There has been a lot of noise recently about Inversion of Control (IoC) with .Net recently (stop sniggering at the back java guys!).... I've been using IoC via the Spring.NET framework for over 2 years now - it's a completely different approach to coding and once you get your head around it everything just falls into place and development is a real joy again. As I mention, Spring.NET is my framework of choice but a recent change in employer has seen me bump up against Castle/Windsor . First impressions are that I like it - it's not as powerful or feature rich as Spring but that's not always a bad thing! The one thing I did miss though was Visual Studio intellisense when editing the configurations - Spring has an online schema that can be associated with a Spring configuration. This got me thinking - if the VS intellisense can be hooked into that easily why not create one for Windsor configuration? So I did...you can download it from my new google code site here . Remem