Designing Android apps for tablets

Question

In the Play developer console it says:

Your APK does not seem to be designed for tablets

But I have added layouts to layout-sw600dp, layout-sw600dp-land, layout-sw720dp and layout-sw720dp-land folders. The complete manifest (as it is):

<?xml version="1.0" encoding="utf-8"?>
<manifest xmlns:android="http://schemas.android.com/apk/res/android"
package="com.technicosa.unjumble"
android:versionCode="1"
android:versionName="1.0" >

<uses-sdk
    android:minSdkVersion="9"
    android:targetSdkVersion="18" />

<supports-screens
    android:anyDensity="true"
    android:largeScreens="true"
    android:normalScreens="true"
    android:resizeable="true"
    android:smallScreens="true"
    android:xlargeScreens="true" />

<application
    android:allowBackup="true"
    android:icon="@drawable/ic_launcher"
    android:label="@string/app_name"
    android:theme="@style/Theme.Sherlock.Light.DarkActionBar" >
    <activity
        android:name="com.technicosa.unjumble.MainActivity"
        android:label="@string/app_name" >
        <intent-filter>
            <action android:name="android.intent.action.MAIN" />

            <category android:name="android.intent.category.LAUNCHER" />
        </intent-filter>
    </activity>
    <activity
        android:name="com.technicosa.unjumble.UserSettingsActivity"
        android:label="@string/title_activity_user_settings" >
    </activity>
</application>

The app runs perfectly on both Nexus 7 and Nexus 10 in the emulator. Also in the developer console under optimization tips it says:

Your Production APK needs to meet the following criteria: Uses available screen space on 10-inch tablets

A screenshot of my app:

While the app seems to run on tablets (I have tested only on emulator), what must be done to fulfill the Play criteria?

Answer 1

I had "Your layout should make use of the available space on tablets" message after uploading first draft of the new application. I've spend an hour trying to change layout of my single activity, tried different folder names, even removed all activities with their layouts - nothing helped. I can confirm @Wytas answer. My problem was that for a draft new app I've uploaded screenshot and promo images which were completely black stub images (meant to be updated later). Once I changed screenshots & promo images to the ones taken from another app (which didn't have that warning message in developer console) the message is gone! I believe Google Play just analyzes screenshots (and maybe promo images) automatically, looking for patches of the uniform color and considers it as bad "layout".

Answer 2

I read somewhere on the play store page that it needs some screenshots for 7" and 10" tablets in order to be featured as "for tablets", whether there is a specific layout for it or not.

Answer 3

Add in file build.grandle

 compile ‘com.android.support:appcompat-v7:19.+’

where 19 - it's compileSdkVersion

Answer 4

I don't believe that this is a completely automated process. In other words, I think there is someone in Google looking at screen shots from your app making a qualitative judgement (probably an intern). This is my reasoning for arriving at that conclusion:

I have three versions of my app (Irish, UK and USA). They are basically the same with different text. The Irish version was released first and initially I encountered that message. I had implemented the manifest (like yours) and had one or two xml files in layout-sw600dp and layout-sw600dp-land and I couldn't see the cause of the problem. I uploaded a new apk with new screen shots (no xml or manifest changes) and the problem went away. Here is the current status of the Irish app: .

Next I implemented the UK version. It displayed "when you did it" as 12th June, the date the APK was uploaded. So at least there is a semblance of consistency in the review process.

Finally - the US version. To reiterate, this is basically the same app with the same xml as the Irish and UK versions and this is my current message:

Now it is quite possible that Google have written some code to look for xmls for large tablets. But if they had, I think my other APKs would be showing that error as well. Therefore, I think that the review process is partly manual.

So my conclusion - a quantitative approach may help (a few more xmls in sw600dp and sw720dp) but don't neglect the qualitative stuff (choose screen shots that don't display empty space !).

Update: re. the "Designed for Phones" message - December 2013

Since I wrote the above Google have introduced the dreaded "Designed for Phones" tagline and "Design your app for tablets" optimisation tips. This appears to be largely based on an automated scan of the apk when you upload it (probably the xml), so the process now seems to be more automated than was previously the case. Here are some points I have discovered which may help others:

1) I was unhappy that Google had designated one of my apps as "designed for phones" and I emailed them and they then removed this designation.

2) On a different app, I was getting the "design your app for 7" tablets" optimisation tip. I added one fragment to my tablet xml in sw600dp like this:

       <FrameLayout
    android:id="@+id/SideTab1"
    android:name="SideTab1"
    android:layout_width="300dp"
    android:layout_height="fill_parent"
    android:layout_marginLeft="20dp"
    /> 

and this did not remove the optimisation tip.

3)However when I made the same change to a second xml in sw600dp then the "design your app for 7" tablets" optimisation tip was replaced by "Your layout should make use of the available space on 10-inch tablets". More importantly, the "designed for phones" designation has now disappeared.

4) Obviously my next step is to make similiar changes in sw720dp.

Things seem to have changed again now (e.g. Google seem to now have removed the "designed for phones" designation in the country in which I am currently residing, and they seem to have relaxed some of their "rules" regarding the "design your app for tablets" message). Apparently, I am now doing "pretty well", which is reassuring news !

Answer 5

After having this same problem and foraging through several forums, what worked for me was changing the targetSDKVersion in the manifest to 11. You can change either minSDKVersion OR targetSDKVersion, as long as one of them is at 11. Also if you use any plugins (like Google Play Services), there's a chance they included their own manifest file somewhere, so make sure ALL the manifest have the same SDK values or your build will not run.

Answer 6

Same in my case like @Wytas and @blackdigger, images were problem too. So I generate the images from http://developer.android.com/distribute/promote/device-art.html then warning message gone.