Good stuff, thanks for the Android dev tip. Found this for iOS: http://blog.manbolo.com/2012/10/30/uirequireddevicecapabilities-and-device-compatibility-matrix
Seems like "If a given capability is optional for your app, do not include the corresponding key in the dictionary," so that answers my question for iOS. https://developer.apple.com/library/ios/documentation/iphone/conceptual/iphoneosprogrammingguide/App-RelatedResources/App-RelatedResources.html Thanks gang! _______________________________________________________________________ Joseph Balderson, Flex & Flash Platform Developer :: http://joeflash.ca Author, Professional Flex 3 :: http://tinyurl.com/proflex3book Joseph Balderson wrote: > Cool, thanks! > > So, does that mean that if you release an app with > <uses-feature android:name="android.hardware.location" > android:required="false" > />, the app store will still allow a user with a non-GPS enabled tablet to > download the app? > > > _______________________________________________________________________ > > Joseph Balderson, Flex & Flash Platform Developer :: http://joeflash.ca > Author, Professional Flex 3 :: http://tinyurl.com/proflex3book > > Frank Dahmen wrote: >> For android it is the "uses-feature" attribute in the manifest >> http://developer.android.com/guide/topics/manifest/uses-feature-element.html >> >> >> >> Am 08.03.2014 19:44, schrieb Joseph Balderson: >>> I noticed that many times, an app in the Android or iOS app store has GPS >>> features, but they are optional. But because the app "uses" GPS, user >>> with >>> non-GPS-enabled tablets cannot download the app. >>> >>> How do you build an app with optional GPS feature, which activates >>> depending on >>> whether the user has it on their device? More specifically, how do you >>> ensure >>> that users with non-GPS enabled tablets can download the app? Is that >>> something >>> you'd establish at the programming level, or in registering the app >>> with the app >>> store? >>> >>> Thanks, >>> >> >
