Gaia/AppPermissions

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

settings":{ "access": "readonly" } but currently not used for anything

clock

• Permissions
  • settings (readwrite, to save/restore audio.volume.alarm setting. Also used to try to intercept hardware volumeup and volumedown events, which the System app doesn't currently pass to apps)
  • attention (to display the alarm ringing screen)

email

• 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.

system

The system app is really part of the platform and can probably never be anything other than a certified app.

wappush

• Permissions
  • settings (read/write) - We need to be able to adjust certain settings when we receive content-provisioning messages, these usually contain APN, POP3 or IMAP settings.
  • wappush - This is needed to receive WAP Push messages.