Mobile/Archive/WebApp Support: Difference between revisions

Latest revision as of 16:43, 11 April 2013

Summary

Provide means to manage web apps in Fennec, based on how Android and Maemo handle adding apps and shortcuts to the desktop.

Current Status

Madhava, Finkle and Fabrice have talked (together and separately) about a direction for webapps. We covered some of the basics, from a user standpoint, as well as some implementation details.

We have a basic idea for how webapps should be exposed.

Next Steps

Implement some prototypes

Team

Design: madhava
Team Members: fabrice

Related Bugs

bug 583750 - [meta] Web apps support in Fennec

Designs

Installing webapps will probably happening within Fennec
Adding a shortcut to the device desktop should happen through the native device mechanism, not from Fennec
Fennec may need to support a "Select a Webapp" UI for native OS shortcut mechanism to use (think "add bookmark to desktop" feature in Android)

Goals/Use Cases

User should be able to install and uninstall webapps.
User should be able to add a shortcut to a webapp on their device desktop
User should be able to launch a webapp from the desktop shortcuts.
Webapps use HTML features, and nothing more

Open Issues

Should "uninstall" be a command _in_ the webapp or built into Fennec?
What packaged webapp formats do we support? or none?
Does this fit into the Mozilla webapp marketplace?

Non Goals

Do not need to be able to launch webapps from inside Fennec
Minimize the amount of webapp UI features exposed directly in Fennec
Do not focus on widget support
Do not add unfriendly APIs for webapps

@@ Line 1: / Line 1: @@
 == Summary ==
-Provide means to allow management of web apps in Fennec.
+Provide means to manage web apps in Fennec, based on how Android and Maemo handle adding apps and shortcuts to the desktop.
 == Current Status ==
-Starting code
+Madhava, Finkle and Fabrice have talked (together and separately) about a direction for webapps. We covered some of the basics, from a user standpoint, as well as some implementation details.
+We have a basic idea for how webapps should be exposed.
 == Next Steps  ==
-# write prototype code
+* Implement some prototypes
-# iterate on UI design
 == Team ==
-* '''Project Lead''': stuart
 * '''Design''': madhava
 * '''Team Members''': fabrice
@@ Line 20: / Line 20: @@
 == Related Bugs ==
-{{bug|XXXXXX}}
+{{bug|583750}} - [meta] Web apps support in Fennec
 == Designs ==
-From a UI point of view, we need several pieces :
+* Installing webapps will probably happening within Fennec
-- a new entry in the site menu, to add/remove a site as an app.
+* Adding a shortcut to the device desktop should happen through the native device mechanism, not from Fennec
-- a new "See all apps" item in the awesomescreen to access the app list.
+* Fennec may need to support a "Select a Webapp" UI for native OS shortcut mechanism to use (think "add bookmark to desktop" feature in Android)
-- an  app list similar to the Bookmarks screen.
 == Goals/Use Cases ==
-The goal is to provide a way to mark a url as being a web app, and allow the user to manage its app list. This goes a bit further than the app tabs on Firefox 4, since this list would persist and be accessible on a dedicated page (or in the the new awesomescreen).
+* User should be able to install and uninstall webapps.
+* User should be able to add a shortcut to a webapp on their device desktop
-Add-ons author should also be able to register a chrome url as an app.
+* User should be able to launch a webapp from the desktop shortcuts.
+* Webapps use HTML features, and nothing more
 == Open Issues ==
-# integration with sync
+* Should "uninstall" be a command _in_ the webapp or built into Fennec?
-# should apps be in tabs like other pages?
+* What packaged webapp formats do we support? or none?
-# how could we notify a user that something changed in a web app, like unread mails count, new events, chat info, etc.? (web notifications will probably help there)
+* Does this fit into the Mozilla webapp marketplace?
-# do we want OS level integration?
-# should we support sites like http://openappmkt.com/ seamlessly, or leverage AMO?
-# do we want to support w3c widgets?
 == Non Goals ==
+* Do not need to be able to launch webapps from inside Fennec
+* Minimize the amount of webapp UI features exposed directly in Fennec
+* Do not focus on widget support
+* Do not add unfriendly APIs for webapps