OK - I was more looking beyond the release at hand and concerned about the "real thing" coming out. How about the build(s) that the carrier (s) deliver(s) to their customers eventually. Say their build is 1.5.x only (to safe space). Such a scenario would be disaster as the apps would be stuck in no-mans-land either running on the G1/1.1, or the new ones only, until all "old" G1/1.1 customers have received their carrier OTA update to reach 1.5.x.
On Apr 13, 9:01 pm, Xavier Ducrohet <[email protected]> wrote: > On Mon, Apr 13, 2009 at 8:53 PM, JP <[email protected]> wrote: > > > Hey, thanks Xavier! > > I've read the blog but I am not clear re: backwards compatibility: > > Will apps currently built against 1.0 or 1.1 run on handsets released > > w/ 1.5, say the new keyboard-less devices? Or do we need to account > > for the changes in 1.5 and re-release? (This would be hell) > > As long as you don't use private APIs you *should* be good (except for > some minor permission changes.) > > That said, we fixed some bugs that may have some minor side effects. > For instance, we changed the minimum size of some widgets in 1.5 that > may impact on your layouts. > > This SDK contains both 1.1 and 1.5, so you should keep compiling your > applications against Android 1.1 but test them on both 1.1 and 1.5 > emulators. > > Xav > -- > Xavier Ducrohet > Android Engineer, Google. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Android Developers" 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/android-developers?hl=en -~----------~----~----~----~------~----~------~--~---
