okay let me explain...I am not affiliated with Google..just a small 3d party contributor.. The whole reasoning was to get new stuff out there and once the UI s

okay let me explain...I am not affiliated with Google..just a small 3d party contributor.. The whole reasoning was to get new stuff out there and once the UI solidified than OEMs would update to latest as they no longer would be using customized UIs ..what you are seeing is the very beginning of that process..the market with new 4.0 devices selling will help get OEMs to that point in 18 months where we will only see 4.x devices. Why? Most if not all dual core and up are GPU based and with Qualcomm reducing costs on the lower end boards you will see dul cores at the bottom end also at the $50 range per handset. As far as developer-wise yes at first it was confusing..backporting certain stuff than writing to 1.6 with a backported set of ui components but its manageable once you step up and start doing it..and there is an Eclipse extra adt-addons plugin to assist in that it analyzes the api to see if it will work per the min and max target api settings in the manifest