Seems like a work-around for that would be to have a base app that only requests the base permissions, and have it on-demand install an optional add-on that requests the additional permissions. The base app calls into the add-on to do the additional functionality.
On 07/13/10 15:17, Jonas Petersson wrote: > On 07/13/2010 09:05 PM, DonFrench wrote: > > > [Joe's app ] >> So Bluetooth is not necessary to benefit from using your app but those >> whose phones support it can reap the additional Bluetooth benefits >> that you so thoughtfully added, is that it?. Since your app is still >> valuable even without Bluetooth functionality, people with pre-2.0 >> phones should not be prohibited from purchasing it, right? Well, you >> make a good point. > > IMHO, the above case is very similar to the enhancement request I > added almost 6 months ago: > > http://code.google.com/p/android/issues/detail?id=6266 > > Some permissions are non-critical for the application and it should be > possible to flag them as such and then let the application find out > whether it was given or not and adjust accordingly. > > So far only 51 people seem to have agreed with me, so either I'm wrong > or most people have not realized why this would be significant > enhancement. > > Best / Jonas > -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
