Home
| Calendar
| Mail Lists
| List Archives
| Desktop SIG
| Hardware Hacking SIG
Wiki | Flickr | PicasaWeb | Video | Maps & Directions | Installfests | Keysignings Linux Cafe | Meeting Notes | Linux Links | Bling | About BLU |
Shankar Viswanathan wrote: > Android apps. In addition to the idea of having a common ad network > framework (mentioned elsewhere in this thread), I feel there is Which Google provides. It's called the Google Mobile Ads SDK. > another way we could make the permissions work for everyone. Consider > a two-tiered permission system consisting of: 1. Required This won't fly. App developers currently have one set of rules to work within: they request a set of permissions from the software management system. If the user accepts the requirements then the Play Store installs the app. If the user denies the requirements then the application will not be installed at all. Simple. What you are suggesting is complicated for users who typically don't understand the differences between, say, unlimited network access and unlimited baseband network access. They're going to be confused when the Play Store asks them twice about these permissions thingies when all they want is their Angry Birds or whatever this month's flavor happens to be. What you are suggesting is complicated for developers who often enough are lazy and unscrupulous. Your proposal introduces at least two different, possibly conflicting, possibly /changing/ environments for every user. It's bad enough that when someone asks for an Android version of an application the initial response is "which Android?" Developers won't bother with optional permissions. It'll be all or nothing. And to be honest? That's the right way to do it from a development and QA perspective even if it is a poor practice. The unscrupulous ones? They'll figure out ways to game the system regardless of the protections. -- Rich P.
BLU is a member of BostonUserGroups | |
We also thank MIT for the use of their facilities. |