Merge "docs: Aded uses-feature to multiple Google Play APK Filtering. Bug: 12271954" into klp-docs

1 files changed, 12 insertions, 0 deletions

diff --git a/docs/html/google/play/publishing/multiple-apks.jd b/docs/html/google/play/publishing/multiple-apks.jd
index 3c7ed0f..ab08e6f 100644
--- a/docs/html/google/play/publishing/multiple-apks.jd
+++ b/docs/html/google/play/publishing/multiple-apks.jd
@@ -82,6 +82,7 @@ APK. </p>
 <ul>
   <li>Support different OpenGL texture compression formats with each APK.</li>
   <li>Support different screen sizes and densities with each APK.</li>
+  <li>Support different device feature sets with each APK.</li>
   <li>Support different platform versions with each APK.</li>
   <li>Support different CPU architectures with each APK (such as for ARM, x86, and MIPS, when your
   app uses the <a href="{@docRoot}tools/sdk/ndk/index.html">Android NDK</a>).</li>
@@ -248,6 +249,17 @@ If you can't avoid using both, be aware that for any conflicts in agreement betw
   <br/>
   </li>
 
+  <li><strong>Device feature sets</strong>
+    <p>This is based on your manifest file's <a 
+href="{@docRoot}guide/topics/manifest/uses-feature-element.html">{@code &lt;uses-feature&gt;}</a> 
+element(s).</p>
+    <p>For example, you can provide one APK for devices that support multitouch and another
+APK for devices that do not support multitouch. See 
+<a href="{@docRoot}guide/topics/manifest/uses-feature-element.html#features-reference">Features
+Reference</a> for a list of features supported by the platform.</p>
+  <br/>
+  </li>
+
   <li><strong>API level</strong>
     <p>This is based on your manifest file's <a
 href="{@docRoot}guide/topics/manifest/uses-sdk-element.html">{@code &lt;uses-sdk&gt;}</a> element.