You say, "I believe". But as TrekKing already implied with his question, this is important enough that it should be documented somewhere without such a cautionary qualification -- if it is in fact true. And if it turns out not to be true, then you should post a follow up to your own comment explaining that you found out it is not true.
Otherwise a lot of people are going to waste a lot of time trying to figure out whether or not it is really true -- or trying to contain the damage when their customers get a surprising version of the software downloaded to the phone. On Jan 17, 10:18 am, Dianne Hackborn <[email protected]> wrote: > Oh and I believe on Market that if you put up a new version of your app with > a higher minSdkVersion, the most recent older version will still be visible > to older devices. That is, the .apks you upload are never deleted; a new > version just supersedes an older one for the devices it is compatible with. > > On Mon, Jan 17, 2011 at 10:14 AM, Dianne Hackborn <[email protected]>wrote: > > > > > By @dimens do you mean the "dp" unit in layouts? > > > If there is something not working on a device, we'd like to know about it > > because it is not compatible with the CDD which is a requirement for having > > Market. > > > On Mon, Jan 17, 2011 at 9:40 AM, Kostya Vasilyev <[email protected]>wrote: > > >> I'm using @dimens quite a bit, not because I have different values for > >> different screen sizes / resolutions, but because it lets me tweak my > >> layouts more easily during development. > > >> After seeing them not work on a certain 1.5 device (even though that's > >> part of API level 1), I've decided that the extra 5% is not worth the > >> trouble. > > >> -- Kostya > > >> 2011/1/17 String <[email protected]> > > >> On Monday, January 17, 2011 3:27:02 PM UTC, Kostya Vasilyev wrote: > > >>> For now, both my apps continue to support 1.5, but a new project I'm > >>>> working on will only run on 1.6+ - because that's the first version with > >>>> multi-resolution support, and one really needs that these days. > > >>> What are you doing with multi-resolution that's problematic? I have quite > >>> a bit of multi-resolution code, and so far the vast majority has degraded > >>> pretty gracefully on 1.5. > > >>> String > >>> -- > >>> 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]<android-developers%[email protected]> > >>> For more options, visit this group at > >>>http://groups.google.com/group/android-developers?hl=en > > >> -- > >> 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]<android-developers%[email protected]> > >> For more options, visit this group at > >>http://groups.google.com/group/android-developers?hl=en > > > -- > > Dianne Hackborn > > Android framework engineer > > [email protected] > > > Note: please don't send private questions to me, as I don't have time to > > provide private support, and so won't reply to such e-mails. All such > > questions should be posted on public forums, where I and others can see and > > answer them. > > -- > Dianne Hackborn > Android framework engineer > [email protected] > > Note: please don't send private questions to me, as I don't have time to > provide private support, and so won't reply to such e-mails. All such > questions should be posted on public forums, where I and others can see and > answer them. -- 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
