>>>>Sort of seems like an a**-backwards way of looking at it to me :-}.
>>>>I'd start by looking at what I wanted to achieve in the project, assess the best platform to give the required functionality and only then start looking at test hardware (although maybe the breadth of hardware choice would be a factor earlier on) But I suppose it depends on the project - if you know that you can dictate the hardware then maybe that's different.....
>>>
>>>more than one edge to this... while you have to verify that your chosen platform is capable of fulfilling the task,
>>>acceptance of the device as a whole IS an important factor in devices like laptops/netbooks, pads and cell phones.
>>>Even if the app performs brilliantly, destroyed word documents can sour people to the device...
>>>For non enterprize/inHouse dev, showing off on a sexy device goes a long way.
>>
>>Guess, to a certain extent, it depends on what Jos is planning.
>>The extreme extension of 'hardware first' would be to find a device that you liked and then try to think of an app for it. I suppose that's that happens with the IPhone :-}
>
>Viv, this is really so simple - we all have preferences for programming on our desktops; I like Lenovo, someone else likes the Dell, whatever. So what mobile phone do you like to work with the most? Accept that if we want to develop iPhone apps then iPhone is the only choice we have. But for Android, Windows Mobile apps there are many choices. Is there one which is better than another for some reason; screen size, usability, reliability, etc?

Hey, I'm not trying to talk you out of your approach - just saying, admittedly without knowing your circumstances, that I'd go about it differently...
As to what mobile phone I like to work with I 'fess up and admit I've programmed none of them though I've done a bit of development for PDAs using .NET
FWIW my own mobile is about 10 years old and gets used about once a week :-}