From 980edc3ca162fd95665b076b67128a43f77f87cf Mon Sep 17 00:00:00 2001
From: Ricardo Cervera
Date: Wed, 15 Jan 2014 11:25:10 -0800
Subject: [PATCH] docs: Aded uses-feature to multiple Google Play APK
Filtering. Bug: 12271954
Change-Id: I6c247e172b2a6dd0ef25afc6cf33f0960fc0fa8d
Review: http://quixote.mtv.corp.google.com:8101/google/play/publishing/multiple-apks.html
---
docs/html/google/play/publishing/multiple-apks.jd | 12 ++++++++++++
1 file changed, 12 insertions(+)
diff --git a/docs/html/google/play/publishing/multiple-apks.jd b/docs/html/google/play/publishing/multiple-apks.jd
index 3c7ed0f4e9300..ab08e6f14afa0 100644
--- a/docs/html/google/play/publishing/multiple-apks.jd
+++ b/docs/html/google/play/publishing/multiple-apks.jd
@@ -82,6 +82,7 @@ APK.
- Support different OpenGL texture compression formats with each APK.
- Support different screen sizes and densities with each APK.
+ - Support different device feature sets with each APK.
- Support different platform versions with each APK.
- Support different CPU architectures with each APK (such as for ARM, x86, and MIPS, when your
app uses the Android NDK).
@@ -248,6 +249,17 @@ If you can't avoid using both, be aware that for any conflicts in agreement betw
+ - Device feature sets
+
This is based on your manifest file's {@code <uses-feature>}
+element(s).
+ For example, you can provide one APK for devices that support multitouch and another
+APK for devices that do not support multitouch. See
+Features
+Reference for a list of features supported by the platform.
+
+
+
- API level
This is based on your manifest file's {@code <uses-sdk>} element.