Features/Mobile/webapps: Difference between revisions

(Created page with "<section begin="status" /> {| class="fullwidth-table" |- | style="font-weight: bold; background: #DDD;" | Feature | style="font-weight: bold; background: #DDD;" | Status | st...")
 
No edit summary
 
(31 intermediate revisions by 5 users not shown)
Line 1: Line 1:
<section begin="status" />
{{FeatureStatus
|Feature name=Web Apps integration in Firefox for Android
|Feature stage=Development
|Feature status=In progress
|Feature version=Firefox 8
|Feature health=OK
|Feature status note=Basic support landed in Firefox 8. Additional work in progress for Firefox 9.
}}
{{FeatureTeam
|Feature product manager=Thomas Arend
|Feature feature manager=Mark Finkle
|Feature lead engineer=Fabrice Desre, Mark Finkle
|Feature accessibility lead=David Bolter
|Feature qa lead=Aaron Train
|Feature ux lead=Madhava Enros
}}
{{FeaturePageBody
|Feature open issues and risks==== Next steps ===
* Implement the frontend pieces to expose webapps in Firefox for Android (find more mocks [https://wiki.mozilla.org/Features/Mobile/webapps#Designs below]):


{| class="fullwidth-table"
*Complete UI&nbsp;design concept
|-
*Implement and review UI design
| style="font-weight: bold; background: #DDD;" | Feature
*Sync with Appetizer team
| style="font-weight: bold; background: #DDD;" | Status
*Feature implementation
| style="font-weight: bold; background: #DDD;" | ETA
**add an "Install web app" entry in the site menu when not in a web app
| style="font-weight: bold; background: #DDD;" | Owner
**handle a --webapp switch on the command line
|-
**minimize the chrome when in web app mode. The icon is still clickable to show the site menu.
| [[https://wiki.mozilla.org/Mobile/Features/webapps Web Apps integration with Firefox for Android]]
**new "Set Page as Web App" entry in the site menu
| {{StatusHealthy|status=One or two sentence status report.}}
**"See all Web Apps" entry in the awesomscreen
| 2011-09-01
**A list-oriented display of the web apps.- new "Set Page as Web App" entry in the site menu
| Thomas Arend
**"See all Web Apps" entry in the awesomscreen
<section end="status" />
**A list-oriented display of the web apps.
**do not go fullscreen on maemo so the normal maemo application bar is used across the top
**completely hide the fennec URL bar
**no site menu at all


|}
=== Risks ===
Note that the awesomescreen is changing, very soon: [https://wiki.mozilla.org/Mobile/Projects/AwesomeScreen2.0 https://wiki.mozilla.org/Mobile/Projects/AwesomeScreen2.0]
|Feature overview=Webapps integration on mobile has (or can have) three principal components:


== Summary  ==
# The ability, within Firefox, for a user to designate a particular website or webapp as having "app status." In desktop Firefox, the analagous action results in the creation of an App Tab (though there are future plans to have the designation mean more than simply a pinned tab).
# Apps should be available for launch, at which point they come up in chromeless instance of Firefox. Two possibilities for where they are available are: 1. on the desktop, like other apps, or 2. within a Firefox Android desktop widget.
# The surfacing of launchpoints, within Firefox itself, in some visually distinct way of sites/apps the user has designated as apps.


Implement the frontend pieces to expose webapps in Firefox for Android.  
Along side of this, there is the issue of handling apps that are installed (i.e. web apps with manifests, etc.) from the web or a webapp store.


== Team  ==
The high level goals for the feature is to expose web apps to users of Firefox for Android.&nbsp;Users should be able to access their apps, to discover new apps, and to have a seemless online apps experience across devices.
|Feature users and use cases=# Frequent use of a certain site makes the user want to allow quick access to it (i.e. not through the browser)
# Frequent use of a certain site make the user want to switch back and forth to it using the system app switching mechanism
# User installs a webapp (i.e. one with a manifest) as an explicit action and then wants to launch and use that webapp
|Feature dependencies=* {{Bug|583750}} - Tracking bug for web app support in Fennec
* <s>{{Bug|584767}}</s> (FIXED in Fx8) - Basic web-app front-end
* <s>{{Bug|663571}}</s> (FIXED in Fx8) - Basic web-app back-end
* {{Bug|609043}} (ASSIGNED) - Add support for Mozilla Labs' new Open Web Apps manifest format and API
|Feature ux design==== Case 1 - Enabling designation of an "app" ===


Who's working on this?
A user should be able to say "I would like to treat this site as an app", most likely from the Site button.


*'''Feature Manager''': ''whoever is responsible for doing the day-to-day work of driving the feature to completion and updating the status on this page''
Prototype patches:
*'''Lead Developer''':  
* [http://people.mozilla.com/~mfinkle/fennec/screenshots/fennec-webapp-01.png screenshot of very rough site menu with "Install as app" item]
*'''Product Manager''':
* [http://people.mozilla.com/~mfinkle/fennec/screenshots/fennec-webapp-02.png screenshot of confirmation / permissions granting dialog]
*'''QA''':
*'''UX''':
*'''Accessibility''':
*'''Security''':
*'''Privacy''':
*Etc.


Team list should make it clear who to ask about what, and who to ping when they're needed. If you do not need someone in a particular role (ie: Security), that's fine, just delete that line. Contact info for each person would also be handy.
==== Older designs ====


== Release Requirements  ==
*[https://bug584767.bugzilla.mozilla.org/attachment.cgi?id=463221 site menu item]


Complete checklist of items that need to be satisfied before we can call this feature "done".
=== Case 2 - Launching apps on Android ===


== Next Steps &amp; Open Issues  ==
==== Android Widget ====


Either the next set of tasks that need to happen to move this project along, or (ideally) the full list of project tasks/action items with things crossed off as they're finished. Including the name of who's responsible for each item, and a rough ETA can be useful.  
The concept here is for an Android-native Firefox widget to be installed with Firefox. It would placed on the Android desktop and could house the icons for installed/designated webapps (as well as potentially other Firefox capabilities like awesomebar suggestions).


Open issues include unanswered questions, things that need to be explored, decisions that still need to be made, etc. Again, including the name of who's responsible for each item can be useful.  
[http://www.flickr.com/photos/madhava_work/5864013195/ http://farm4.static.flickr.com/3142/5864013195_f726e2cb4d.jpg]


== Related Bugs &amp; Dependencies  ==
[http://www.flickr.com/photos/madhava_work/5864481780/ http://farm6.static.flickr.com/5111/5864481780_45651ab1e8.jpg]


Links to the feature tracking bug &amp; other relevant bugs; links to related plans (test plan, product marketing plan, etc.); notes about things that depend on this, etc.


== Risks  ==
'''Related question''': How much of awesomebar capability should be available through the widget?


Identify, prioritize, track and communicate any risks associated with this feature/project.  
Example:
[http://www.flickr.com/photos/madhava_work/5434008892/ http://farm5.static.flickr.com/4139/5434008892_9f4bd604bf.jpg]


== Use Cases  ==


Everyone loves use cases, so you should provide them if you can (and where it makes sense). The [[ChannelSwitching/ChannelSwitchingFeature#Use_Cases|Channel Switcher]] Feature Page has some good examples.
More here: http://www.flickr.com/photos/madhava_work/sets/72157625893411005/


== Designs  ==
==== Direct launch from Android Desktop ====


Any and all mockups, design specs, tech specs, etc. Either inline or linked to.  
The design, in this case, is clear -- icons based on high-res-as-available versions of the site favicon, directly on the desktop.


== Test Plans  ==
=== Case 3 - Apps available in the browser ===


Any and all test plans and strategies. Either inline or linked to.  
Even if installed/designated apps are made available on the desktop or in a desktop widget, there is still value to them being synced and being findable in the browser itself. The awesomescreen and tab area are two possibilities. We're exploring the former more vigorously.


== Goals  ==
This could include:
* An icon to show which awesomebar results are designated as apps (like icons right now indicate which results are open in a tab or are bookmarks)
* An awesomescreen category of just apps
* Apps bubbling up in the pre-typing awesomescreen list, given higher scores as bookmarks get right now


The high level goals for the feature (which the release requirements checklist should fulfill). These are the guiding light and overall vision for the feature. Refer to this if there is confusion or are disputes about direction, designs, planning, etc.
==== older designs ====
These are old - do not implement!


== Non-Goals  ==
[[Image:Webapps-category.png|477x298px|Webapps-category.png]]


Things we are specifically not doing or building as part of this feature.  
*[https://bug584767.bugzilla.mozilla.org/attachment.cgi?id=464055 Mockup 1]
 
*[https://bug584767.bugzilla.mozilla.org/attachment.cgi?id=464056 Mockup 2]
== Other Stuff  ==
*[https://bug584767.bugzilla.mozilla.org/attachment.cgi?id=463222 Mockup 4]
 
*[https://bug584767.bugzilla.mozilla.org/attachment.cgi?id=463224 Mockup 5]
Can include things like:  
*[https://bug584767.bugzilla.mozilla.org/attachment.cgi?id=463580 Mockup 6]
 
}}
*Competitive landscape
{{FeatureInfo
*Research &amp; references
|Feature priority=P1
*Whatever else is useful to the project.
|Feature roadmap=Firefox Mobile
 
|Feature list=Mobile
== Legend (remove if you like)  ==
|Feature engineering team=Mobile front-end
 
}}
{| class="fullwidth-table"
{{FeatureTeamStatus
|-
|Feature security status=sec-review-needed
| {{StatusHealthy|status=&nbsp;}}
|Feature security health=Assigned
| Healthy: feature is progressing as expected.
|Feature security notes=imelven
|-
|Feature qa status=[https://wiki.mozilla.org/Features/Mobile/webapps/TestPlan Testplan]
| {{StatusBlocked|status=&nbsp;}}  
|Feature qa notes=Testplan in progress
| Blocked: feature is currently blocked.
}}
|-
| {{StatusAtRisk|status=&nbsp;}}
| At Risk: feature is at risk of missing its targeted release.
|-
| '''ETA'''
| Estimated date for completion of the current feature task. Overall ETA for the feature is the product release date.
|}
 
__NOTOC__
 
Please remove this line and any non-relevant categories below. Add whatever other categories you feel are appropriate.  
 
[[Category:Features]] [[Category:Firefox]] [[Category:Platform]] [[Category:Services]] [[Category:Mobile]] [[Category:Other]]

Latest revision as of 00:23, 13 October 2011

Please use "Edit with form" above to edit this page.

Status

Web Apps integration in Firefox for Android
Stage Development
Status In progress
Release target Firefox 8
Health OK
Status note Basic support landed in Firefox 8. Additional work in progress for Firefox 9.

{{#set:Feature name=Web Apps integration in Firefox for Android

|Feature stage=Development |Feature status=In progress |Feature version=Firefox 8 |Feature health=OK |Feature status note=Basic support landed in Firefox 8. Additional work in progress for Firefox 9. }}

Team

Product manager Thomas Arend
Directly Responsible Individual Mark Finkle
Lead engineer Fabrice Desre, Mark Finkle
Security lead `
Privacy lead `
Localization lead `
Accessibility lead David Bolter
QA lead Aaron Train
UX lead Madhava Enros
Product marketing lead `
Operations lead `
Additional members `

{{#set:Feature product manager=Thomas Arend

|Feature feature manager=Mark Finkle |Feature lead engineer=Fabrice Desre, Mark Finkle |Feature security lead=` |Feature privacy lead=` |Feature localization lead=` |Feature accessibility lead=David Bolter |Feature qa lead=Aaron Train |Feature ux lead=Madhava Enros |Feature product marketing lead=` |Feature operations lead=` |Feature additional members=` }}

Open issues/risks

Next steps

  • Implement the frontend pieces to expose webapps in Firefox for Android (find more mocks below):
  • Complete UI design concept
  • Implement and review UI design
  • Sync with Appetizer team
  • Feature implementation
    • add an "Install web app" entry in the site menu when not in a web app
    • handle a --webapp switch on the command line
    • minimize the chrome when in web app mode. The icon is still clickable to show the site menu.
    • new "Set Page as Web App" entry in the site menu
    • "See all Web Apps" entry in the awesomscreen
    • A list-oriented display of the web apps.- new "Set Page as Web App" entry in the site menu
    • "See all Web Apps" entry in the awesomscreen
    • A list-oriented display of the web apps.
    • do not go fullscreen on maemo so the normal maemo application bar is used across the top
    • completely hide the fennec URL bar
    • no site menu at all

Risks

Note that the awesomescreen is changing, very soon: https://wiki.mozilla.org/Mobile/Projects/AwesomeScreen2.0

Stage 1: Definition

1. Feature overview

Webapps integration on mobile has (or can have) three principal components:

  1. The ability, within Firefox, for a user to designate a particular website or webapp as having "app status." In desktop Firefox, the analagous action results in the creation of an App Tab (though there are future plans to have the designation mean more than simply a pinned tab).
  2. Apps should be available for launch, at which point they come up in chromeless instance of Firefox. Two possibilities for where they are available are: 1. on the desktop, like other apps, or 2. within a Firefox Android desktop widget.
  3. The surfacing of launchpoints, within Firefox itself, in some visually distinct way of sites/apps the user has designated as apps.

Along side of this, there is the issue of handling apps that are installed (i.e. web apps with manifests, etc.) from the web or a webapp store.

The high level goals for the feature is to expose web apps to users of Firefox for Android. Users should be able to access their apps, to discover new apps, and to have a seemless online apps experience across devices.

2. Users & use cases

  1. Frequent use of a certain site makes the user want to allow quick access to it (i.e. not through the browser)
  2. Frequent use of a certain site make the user want to switch back and forth to it using the system app switching mechanism
  3. User installs a webapp (i.e. one with a manifest) as an explicit action and then wants to launch and use that webapp

3. Dependencies

  • bug 583750 - Tracking bug for web app support in Fennec
  • bug 584767 (FIXED in Fx8) - Basic web-app front-end
  • bug 663571 (FIXED in Fx8) - Basic web-app back-end
  • bug 609043 (ASSIGNED) - Add support for Mozilla Labs' new Open Web Apps manifest format and API

4. Requirements

`

Non-goals

`

Stage 2: Design

5. Functional specification

`

6. User experience design

Case 1 - Enabling designation of an "app"

A user should be able to say "I would like to treat this site as an app", most likely from the Site button.

Prototype patches:

Older designs

Case 2 - Launching apps on Android

Android Widget

The concept here is for an Android-native Firefox widget to be installed with Firefox. It would placed on the Android desktop and could house the icons for installed/designated webapps (as well as potentially other Firefox capabilities like awesomebar suggestions).

5864013195_f726e2cb4d.jpg

5864481780_45651ab1e8.jpg


Related question: How much of awesomebar capability should be available through the widget?

Example: 5434008892_9f4bd604bf.jpg


More here: http://www.flickr.com/photos/madhava_work/sets/72157625893411005/

Direct launch from Android Desktop

The design, in this case, is clear -- icons based on high-res-as-available versions of the site favicon, directly on the desktop.

Case 3 - Apps available in the browser

Even if installed/designated apps are made available on the desktop or in a desktop widget, there is still value to them being synced and being findable in the browser itself. The awesomescreen and tab area are two possibilities. We're exploring the former more vigorously.

This could include:

  • An icon to show which awesomebar results are designated as apps (like icons right now indicate which results are open in a tab or are bookmarks)
  • An awesomescreen category of just apps
  • Apps bubbling up in the pre-typing awesomescreen list, given higher scores as bookmarks get right now

older designs

These are old - do not implement!

 

Stage 3: Planning

7. Implementation plan

`

8. Reviews

Security review

`

Privacy review

`

Localization review

`

Accessibility

`

Quality Assurance review

`

Operations review

`

Stage 4: Development

9. Implementation

`

Stage 5: Release

10. Landing criteria

` {{#set:Feature open issues and risks==== Next steps ===

  • Implement the frontend pieces to expose webapps in Firefox for Android (find more mocks below):
  • Complete UI design concept
  • Implement and review UI design
  • Sync with Appetizer team
  • Feature implementation
    • add an "Install web app" entry in the site menu when not in a web app
    • handle a --webapp switch on the command line
    • minimize the chrome when in web app mode. The icon is still clickable to show the site menu.
    • new "Set Page as Web App" entry in the site menu
    • "See all Web Apps" entry in the awesomscreen
    • A list-oriented display of the web apps.- new "Set Page as Web App" entry in the site menu
    • "See all Web Apps" entry in the awesomscreen
    • A list-oriented display of the web apps.
    • do not go fullscreen on maemo so the normal maemo application bar is used across the top
    • completely hide the fennec URL bar
    • no site menu at all

Risks

Note that the awesomescreen is changing, very soon: https://wiki.mozilla.org/Mobile/Projects/AwesomeScreen2.0 |Feature overview=Webapps integration on mobile has (or can have) three principal components:

  1. The ability, within Firefox, for a user to designate a particular website or webapp as having "app status." In desktop Firefox, the analagous action results in the creation of an App Tab (though there are future plans to have the designation mean more than simply a pinned tab).
  2. Apps should be available for launch, at which point they come up in chromeless instance of Firefox. Two possibilities for where they are available are: 1. on the desktop, like other apps, or 2. within a Firefox Android desktop widget.
  3. The surfacing of launchpoints, within Firefox itself, in some visually distinct way of sites/apps the user has designated as apps.

Along side of this, there is the issue of handling apps that are installed (i.e. web apps with manifests, etc.) from the web or a webapp store.

The high level goals for the feature is to expose web apps to users of Firefox for Android. Users should be able to access their apps, to discover new apps, and to have a seemless online apps experience across devices. |Feature users and use cases=# Frequent use of a certain site makes the user want to allow quick access to it (i.e. not through the browser)

  1. Frequent use of a certain site make the user want to switch back and forth to it using the system app switching mechanism
  2. User installs a webapp (i.e. one with a manifest) as an explicit action and then wants to launch and use that webapp

|Feature dependencies=* bug 583750 - Tracking bug for web app support in Fennec

  • bug 584767 (FIXED in Fx8) - Basic web-app front-end
  • bug 663571 (FIXED in Fx8) - Basic web-app back-end
  • bug 609043 (ASSIGNED) - Add support for Mozilla Labs' new Open Web Apps manifest format and API

|Feature requirements=` |Feature non-goals=` |Feature functional spec=` |Feature ux design==== Case 1 - Enabling designation of an "app" ===

A user should be able to say "I would like to treat this site as an app", most likely from the Site button.

Prototype patches:

Older designs

Case 2 - Launching apps on Android

Android Widget

The concept here is for an Android-native Firefox widget to be installed with Firefox. It would placed on the Android desktop and could house the icons for installed/designated webapps (as well as potentially other Firefox capabilities like awesomebar suggestions).

5864013195_f726e2cb4d.jpg

5864481780_45651ab1e8.jpg


Related question: How much of awesomebar capability should be available through the widget?

Example: 5434008892_9f4bd604bf.jpg


More here: http://www.flickr.com/photos/madhava_work/sets/72157625893411005/

Direct launch from Android Desktop

The design, in this case, is clear -- icons based on high-res-as-available versions of the site favicon, directly on the desktop.

Case 3 - Apps available in the browser

Even if installed/designated apps are made available on the desktop or in a desktop widget, there is still value to them being synced and being findable in the browser itself. The awesomescreen and tab area are two possibilities. We're exploring the former more vigorously.

This could include:

  • An icon to show which awesomebar results are designated as apps (like icons right now indicate which results are open in a tab or are bookmarks)
  • An awesomescreen category of just apps
  • Apps bubbling up in the pre-typing awesomescreen list, given higher scores as bookmarks get right now

older designs

These are old - do not implement!

 

|Feature implementation plan=` |Feature security review=` |Feature privacy review=` |Feature localization review=` |Feature accessibility review=` |Feature qa review=` |Feature operations review=` |Feature implementation notes=` |Feature landing criteria=` }}

Feature details

Priority P1
Rank 999
Theme / Goal `
Roadmap Firefox Mobile
Secondary roadmap `
Feature list Mobile
Project `
Engineering team Mobile front-end

{{#set:Feature priority=P1

|Feature rank=999 |Feature theme=` |Feature roadmap=Firefox Mobile |Feature secondary roadmap=` |Feature list=Mobile |Feature project=` |Feature engineering team=Mobile front-end }}

Team status notes

  status notes
Products ` `
Engineering ` `
Security sec-review-needed imelven
Privacy ` `
Localization ` `
Accessibility ` `
Quality assurance Testplan Testplan in progress
User experience ` `
Product marketing ` `
Operations ` `

{{#set:Feature products status=`

|Feature products notes=` |Feature engineering status=` |Feature engineering notes=` |Feature security status=sec-review-needed |Feature security health=Assigned |Feature security notes=imelven |Feature privacy status=` |Feature privacy notes=` |Feature localization status=` |Feature localization notes=` |Feature accessibility status=` |Feature accessibility notes=` |Feature qa status=Testplan |Feature qa notes=Testplan in progress |Feature ux status=` |Feature ux notes=` |Feature product marketing status=` |Feature product marketing notes=` |Feature operations status=` |Feature operations notes=` }}