i'm developing on version 14 with minsdk declared of 10 (recently up from 8). my biggest user categories are tablets according to my dashboard. according to the docs, I need minsdk declaration of 11, among several other things, for tablets to use my apps. in response to "Can you site where this is specified?": my development console keeps alerting me to increase my minsdk to 11 and directing me to this page for "what I need to fix: https://play.google.com/apps/publish/?dev_acc=15292212472185785944#OptimizationsPlace:p=com.ogradythemaze which then directs me to this page for: "*Design your app for tablets **Show details* <javascript:void(0)>":-The minimum Android version and target Android version need to support tablets (check targetSdkVersion and minSdkVersion). *Learn more*<http://developer.android.com/distribute/googleplay/quality/tablet.html#android-versions> ": http://developer.android.com/distribute/googleplay/quality/tablet.html#android-versions which has a long detailed list of 12 things needed for tablet support, including in Part 8;
At a minimum, check the *<uses-sdk>*<http://developer.android.com/guide/topics/manifest/uses-sdk-element.html>element to make sure that: 1. targetSdkVersion is declared with value 11 or higher (14 or higher is recommended), OR 2. minSdkVersion is declared with value 11 or higher. 3. If a maxSdkVersion attribute is declared, it must have a value of 11 or higher. Note that, in general, the use of maxSdkVersion is *not recommended* *I cannot afford a actual tablet to test on, so I use the emulator which worked for my 3D surfaceveiw, layout free, game. also I see most of my users are tablets. from this I figure my code works even though initially I had done none of the 12 steps for tablets. I dont' think i'm using any special features unique to high versions. i'm still curious as to whether the executable is different for different minimumsdk when developed on the same skd (14 at the moment).* On Monday, October 28, 2013 10:27:49 AM UTC-5, TreKing wrote: > > On Mon, Oct 28, 2013 at 9:26 AM, firebreather > <michaelir...@gmail.com<javascript:> > > wrote: > >> info seems fuzzy on the impact of changing minsdkversion declaration, >> particularly in the android docs, where it appears to just limit the number >> of phones the app site will allow to download your app. if that was the >> case then you'd think everyone would just declare minsdk of 1. >> > > That would mean having to account for a huge number of API changes > throughout the Android lifetime, and having to test a massive list of > devices and configurations, which is bad enough already. > >> > >> i'm developing on version 14 with minsdk declared of 10 (recently up from >> 8). my biggest user categories are tablets according to my dashboard. >> according to the docs, I need minsdk declaration of 11, among several other >> things, for tablets to use my apps. >> > > Can you site where this is specified? > > Tablet support was introduced in Android 3.0. By "support", this means > official APIs designed to take advantage of the larger screen space (i.e, > Fragments and more resource qualifiers). That DOES not mean that tablets > can't run older apps. They run just fine - they just end up looking like > really huge phones. > > >> is this bad information? why can tablets use my app now if 11 is really >> needed? >> > > In short, it's "needed" for the newer APIs that facilitate tablet > development. They are not needed to just run the apps period. Moreover, > with the Support Library, you can use many of those new APIs as far back as > Android 1.6. So you "need" to target 11 if you're targeting tablets and are > not using the support library. > > >> will raising the min to 11 change the executable code, improving the run >> time for my games on version 11 and up phones and tablets? >> > > The target SDK tells the system what is the highest level you've > confidently developed and tested on (usually based on your own device(s)). > If you target something smaller, but run on something larger, the system > runs in a compatibility mode that makes sure the app runs correctly on the > newer platform. This might, and probably does, incur some overhead, though > I'm not really sure about the specific details. > > > ------------------------------------------------------------------------------------------------- > 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 --- You received this message because you are subscribed to the Google Groups "Android Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to android-developers+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
