Well, in a certain important sense, yes, 2.0 is 'obsolete'. But I am afraid people will read this out of context, so I have to object here: any Android developer should still keep 2.0 in mind as a probable target for his applications, even if never the primary target platform.
That is, most of us should develop using the latest Android 2.3 SDK, but continue to develop applications that will run well on 2.0, 2.1 and 2.2 devices. Unless you need new bug fixes or new APIs available only in a later SDK, I would even say it should run on 1.6 devices. The application I am developing is an example of this: I am using the 2.3 SDK, but the customer will run on a 2.2 phone. So I test on a 2.2 phone. But since the application requires a recent Bluetooth API, I cannot run it on a 1.6 phone, so there is no point in testing it there; except to make sure that it doesn't crash (we have done this test). I have a give-away app, SylloGizmo, that I originally developed for Android 1.5. Now since it is hard to even find a 1.5 phone in the wild anymore, there is not much point in continuing to test it on 1.5. So whenever I touch the code, I test it on 1.6 and up instead. This turned out to be valuable, since I found a layout bug that only appears in 2.1 with a certain choice of screen width and lcd density (I forget the magic combo now). It is getting hard to find 2.0 phones too: curious that by any definition of 'obsolete', 2.0 is more obsolete than 1.6. The Android Market Dashboard, for example, shows no more than .1% of phones connecting are using 2.0 -- if even that many. So summing up: you are right to warn him that no one will consider sample code or tutorial code to be broken just because it doesn't work under 2.0. But we should all continue to test against it, except when our applications require features not available under 2.0. But when we test, since 2.0 is 'obsolete', we should not be overly concerned about minor bugs that show up only in 2.0: worry only about crashers. PS: after seeing the Dashboard, I decided testing against 2.0 is less important than I thought at first. But the conclusion above stands: we should still test against it. I will be keeping my 2.0 AVD, I just won't spend much time on it now that I see how few 2.0 phones there are out there. But I will still use it for quick testing before new releases. On Dec 30, 10:37 am, TreKing <treking...@gmail.com> wrote: > On Sun, Dec 26, 2010 at 7:32 PM, 小浣熊 <qianyan...@gmail.com> wrote: > > These tutorials have the same proplem on displaying images on 2.0 device. > > 2.0 is obsolete, AFAIK. Forget about it. > > ------------------------------------------------------------------------------------------------- > TreKing <http://sites.google.com/site/rezmobileapps/treking> - Chicago > transit tracking app for Android-powered devices -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
