[android-developers] Question about Permissions that Imply Feature Requirements

Hi

  2 of my applications use send_sms/receive_sms permissions. I have business logic in codes to test availability of telephony service and to switch from using phone's SMS function to web/http interface from remote gateway if phone service on device not available (mainly WiFi capable only devices). And I don't want to maintain two codes, one 4 phone and another one for wifi only device, just for this tiny permission requirement difference in AndroidManifest.xml.
  My problem is, according to Android doc, setting of send_sms / receive_sms permission requirement will imply a feature requirement for telephony feature on device which causes my applications being filtered out from market for wifi only devices. This kind of implicit implementation doesn't make sense to me and I think it's better to leave it to developers for them to declare it using <uses-feature> tag explicitly if they feel fit.
  Would Google consider to revise this kind of implicit feature requirement implementation as to me the uses-permission requirement is a must-have (for proper functioning of an app) but uses-feature requirement only a nice-to-have (app should test the feature before using it)? Tie them up together doesn't make sense to me.  In minimum, did anyone have experience before trying to manually set the uses-feature telephony to false just for overwriting this kind of implicit implementation? Which one take precedence if I put false in AndroidManifest.xml?

  Thanks.

--
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscribe@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en