by MichaelEGR » Thu Jan 28, 2010 2:00 am
At this time it is a challenging question to answer.
What are your goals as a developer and how do you want your applications to be used?
Do you want your applications to be compatible with large parts of the Android ecosystem?
How long is your development lifecycle? Will you take an app to market in 1 month, 3 months, or 6? Are you even considering taking an app to market?
If you are doing real time apps and games the benefit from a purely speed/ability direction comes from the latest hardware (Droid & Nexus One). However, the APIs you will use to develop games are readily available on 1.5 OS devices.
There is fragmentation across the Android ecosystem and it lies not so much with the devices themselves, but the variance of OS versions. Even then not so much in API coverage, but underlying implementation of the API that varies across the OSes. While an API might have been introduced in 1.0 it's implementation may not be rock solid to 2.0.1. An example in that direction is Porter-Duff blending in the Android 2D API. There are inconsistent and buggy implementations pre 2.X. Things work as expected 2.X+, but not prior. While there are not all too many variances there are significant ones when it comes to making a real time app/game run across the ecosystem that may be difficult to uncover.
I'd say if you aren't planning on releasing an app for 3-6 months focus on Android 2.x and 1.6. Old standbys on 1.6 are the G1 and Ion/MyTouch3G (in US on T-Mobile). For 1.5 I can't think of a really attractive device, so pick any to test with...
Founder & Principal Architect; EGR Software LLC
http://www.typhonrt.org
http://www.egrsoftware.com