The ideal, surely, is to always write for the most current version of the platform, and develop in such a way that later OS features are automatically and seamlessly disabled/hidden for less able devices. I believe however (getting ready to be shot down) that we don't have full forwards compatibility from earlier versions of Android. Google have matured Android rapidly over the previous 12 months and I get the impression that the early adopters are feeling the pain of that more now than before.
Incidentally I hear that iPhone OS X 4 will not support the first generation iPhone, so it looks like we will see some fragmentation here too. On Jan 19, 11:04 pm, Karsten Silz <[email protected]> wrote: > On 19 Jan., 21:38, Casper Bang <[email protected]> wrote: > > > But how can you target an application for a platform that does not yet > > exist, neither in the SDK or as a physical device? > > You can't, and that's the point - you have to at least re-test or > update your app. > > > But at least with Android, it > > doesn't take 3-4 weeks for a developer to update an application since > > there's no certification process. > > True, but it gets you phishing apps that steal your bank data > (http://www.osnews.com/story/22723).
-- You received this message because you are subscribed to the Google Groups "The Java Posse" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/javaposse?hl=en.
