Gaia/AppPermissions: Difference between revisions
< Gaia
Jump to navigation
Jump to search
(→email) |
(→email) |
||
| Line 18: | Line 18: | ||
== email == | == email == | ||
* Permissions | * Permissions | ||
** settings (read only) - to support "email sent" sound which is controlled by the settings | ** settings (read only) - to support "email sent" sound which is controlled by the settings app per UX decision some time ago. The e-mail app could just control this internally in its own settings. | ||
== findmydevice == | == findmydevice == | ||
Revision as of 17:56, 15 April 2014
What is forcing your Gaia app to be a certified app? Could it be just a privileged app or even a web app? What is currently stopping that from happening?
To find out, take a look at the permissions your app requests in its manifest.webapp file, and compare against the list here. Also, please note any other reasons that your app currently has to be certified.
browser
- Permissions
- settings (read only)
- nfc (read/write)
- Has to run in the main process because we don't have nested processes for content processes.
- Is being replace by the system browser which will be part of the system app.
calendar
camera
clock
communications
costcontrol
- Permissions
- settings (read only) - to support "email sent" sound which is controlled by the settings app per UX decision some time ago. The e-mail app could just control this internally in its own settings.
findmydevice
fm
gallery
homescreen
keyboard
music
pdfjs
search
settings
sms
system
The system app is really part of the platform and can probably never be anything other than a certified app.