>>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 :-}