summaryrefslogtreecommitdiffstats
path: root/docs/html/preview/tv/games/index.jd
diff options
context:
space:
mode:
Diffstat (limited to 'docs/html/preview/tv/games/index.jd')
-rw-r--r--docs/html/preview/tv/games/index.jd52
1 files changed, 43 insertions, 9 deletions
diff --git a/docs/html/preview/tv/games/index.jd b/docs/html/preview/tv/games/index.jd
index 61a26d2c..68d2d8b 100644
--- a/docs/html/preview/tv/games/index.jd
+++ b/docs/html/preview/tv/games/index.jd
@@ -21,7 +21,7 @@ developers. These areas include its large size, its control scheme, and the fact
players are viewing it simultaneously.</p>
-<h2 id=display>Display</h2>
+<h2 id="display">Display</h2>
<p>The two main things to keep in mind when developing games for the TV screen are its nature as a
shared display and the need to design your game for a landscape orientation.</p>
<h3>Shared display</h3>
@@ -105,14 +105,48 @@ Controllers"</a>. Specific information about Bluetooth connections is at <a
href="http://developer.android.com/guide/topics/connectivity/bluetooth.html">Bluetooth</a>.</p>
<h2 id="manifest">Manifest</h2>
-<p>Games are displayed in a separate row from regular apps in the launcher. Android TV uses the
-<code>android:isGame</code> flag to differentiate games from non-game apps. You can assign it a
-value of either <code>true</code> or <code>false</code>. For example:</p>
-<pre class="fragment">&lt;application&gt;
- ...
-&lt; android:isGame=["true" | "false"] &gt;
- ...
-&lt;/application&gt;</pre>
+
+<p>
+ Games are displayed in a separate row from regular apps in the launcher. Android TV uses the
+ <code>android:isGame</code> attribute to differentiate games from non-game apps. Set this value
+ to <code>true</code> in your game's app manifest, as shown in the following code example:
+</p>
+
+<pre class="fragment">
+&lt;application&gt;
+ ...
+ &lt; meta-data android:name="isGame" android:value="true" &gt;
+ ...
+&lt;/application&gt;
+</pre>
+
+
+<h3 id="gamepad">Game Controllers</h3>
+
+<p>
+ Games controllers may not be available or active for users of a TV device. In order to properly
+ inform users that your game requires (or just supports) a game controller, you must include
+ entries in the app manifest. If your game requires a game controller, you must include the
+ following entry in your app manifest:
+</p>
+
+<pre>
+ &lt;uses-feature android:name="android.hardware.gamepad"/&gt;
+</pre>
+
+<p>
+ If your game uses, but does not require, a game controller, include the following feature
+ entry in your app manifest:
+</p>
+
+<pre>
+ &lt;uses-feature android:name="android.hardware.gamepad" android:required="false"/&gt;
+</pre>
+
+<p>For more information about manifest entries, see
+ <a href="{@docRoot}guide/topics/manifest/manifest-intro.html">App Manifest</a>.
+</p>
+
<h2 id="gpgs">Google Play Game Services</h2>
<p>If your game integrates Google Play Game Services, you should keep in mind a number of