177
edits
Changes
→Distribution / management of WebApps
# It should not be trivially easy for a rogue application to be listed on a marketplace / store
# A store may revoke a bad / malicious WebApp
# A user may revoke a bad / malicious WebApp.# A telco can decide which stores to implicitly trust on their devicesthat they sell. (an analogy in debian packaging terms is that the telco sets the initial contents of the /etc/apt/sources.list file)
# A user must be able to override the stores which they decide to implicity trust on their devices. (an analogy in debian packaging terms is that the user should be able to set the contents of the /etc/apt/sources.list file)
# The distribution of applications must scale to mass-volume proportions (100 million or more phones; 1 million or more store-distributed application downloads or updates per day)
# The development of applications must be straightforward, and rapid development cycles must be easy.
# The security of measures chosen to underpin the distribution of applications through stores must not interfere with, or make awkward, the development of applications.# The development of applications by a single developer must not interfere with or compromise the security measures or interfere with the secure distribution of applications via any give storethrough stores.
=== Management / granting of API permissions to WebApps ===
