You'd do <supports-sdk android:minSdkVersion="3" android:targetSdkVersion="4" /> and then configure the rest of the manifest as desired.
On Wed, Sep 9, 2009 at 2:12 AM, Al Sutton <[email protected]> wrote: > > Dianne, > > In the blog post can you cover how to produce one app which will run > on cupcake and donut and support multiple resolutions. > > As I understand things at the moment developers will need at least two > versions of the same app listed in Market to cover both bases; One > with minSDK="4" and the supports-screens manifest tag and a separate > one for cupcake devices because cupcake won't run apps with minSDK > > 3. If there is also a lite & paid for version you're then into 4 app > listings for the same app (lite, paid-for, multi-resolution lite, > multi-resolution paid-for), which seems like its' going to be a it of > a pain. > > Thanks, > > Al. > > > On Sep 9, 7:35 am, Dianne Hackborn <[email protected]> wrote: > > Supporting a wider variety of hardware has been an ongoing processes, and > > was already started with 1.5 with the introduction of soft keyboards and > > corresponding mechanisms for applications to declare they require hard > > keyboards etc. This will continue after Donut as well. > > > > We are not going to drop a hardware requirement without having a > mechanism > > for applications to specify that they need the hardware and a strategy > for > > grand-fathering existing applications into the filtering. > > > > > > > > On Tue, Sep 8, 2009 at 11:26 PM, gasolin <[email protected]> wrote: > > > > > Hello, > > > > > I was thinking there are plenty of hardware constrains in upcoming > > > android devices, > > > not only the screen resolution. There will be some devices without > > > compass, wifi, g-sensor... ,etc. > > > > > It will be nice that developer could pre-claimed the app requirement > > > and user could be notified before they install the app and feel bad > > > while the app hang (mostly without notice). > > > > > Donut's 'supports-screens' tag could be easily extend to this > > > suggested architecture if google guys think its helpful. > > >http://code.google.com/p/android/issues/detail?id=3693 > > > > > Please 'Star' this issue in the above link if you think it's good for > > > android ecosystem. > > > > > regards > > > -- > > > gasolin > > > > -- > > 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 -~----------~----~----~----~------~----~------~--~---
