MozillaWiki

Web Apps integration: Difference between revisions

Page Discussion

Web Apps integration (view source)

Revision as of 19:33, 17 February 2012

8 bytes added ,  17 February 2012
no edit summary
No edit summary
No edit summary
Line 22: Line 22:


* UX (Boriss) has confirmed that there will not be a permanently visible Home Tab. Does this alter the user stories below? Do any assumptions by Product or Apps need to be re-evaluated in light of this?
* UX (Boriss) has confirmed that there will not be a permanently visible Home Tab. Does this alter the user stories below? Do any assumptions by Product or Apps need to be re-evaluated in light of this?
A: (JA) We will only keep the link to the market place on the home tab for FF13.


* Should we open the dashboard after app install? Myk said "The doorhanger prompt seems reasonable and consistent with existing Firefox prompts for similar activities. But opening the dashboard isn't necessarily the right thing to do next. In the addon it feels clunky. It would be good to specify something else here."
* Should we open the dashboard after app install? Myk said "The doorhanger prompt seems reasonable and consistent with existing Firefox prompts for similar activities. But opening the dashboard isn't necessarily the right thing to do next. In the addon it feels clunky. It would be good to specify something else here."
A: (JA) No. There is not dashboard because we are cutting Sync.


* What is the default app opening behavior? Open as app tab? Open full-screen? Customizable? If the app is already open, open new one or activate the existing one?
* What is the default app opening behavior? Open as app tab? Open full-screen? Customizable? If the app is already open, open new one or activate the existing one?
A: (JA) The app is only installed natively so native is the only way to open. If app already open it should reactivate the open app window.


* About "Manual Install button on page that triggers Firefox install flow". Myk asked "Does it mean Firefox would add a button to the content of a page that offers an addon? Or simply that a page can display UI for installing an addon? The former feels underspecified and raises thorny questions that someone from the UX team should work through. The latter is just the natural consequence of having the mozapps API."
* About "Manual Install button on page that triggers Firefox install flow". Myk asked "Does it mean Firefox would add a button to the content of a page that offers an addon? Or simply that a page can display UI for installing an addon? The former feels underspecified and raises thorny questions that someone from the UX team should work through. The latter is just the natural consequence of having the mozapps API."
A: (JA) Do not understand this question. Feels out of scope.


* "App launchers must be able to update their appearance" - This is a web-side feature, so doesn't belong here, correct?
* "App launchers must be able to update their appearance" - This is a web-side feature, so doesn't belong here, correct?
A: (JA) Not sure why appearances would need to be updated, but either way we're not building that now. So it does not below here.


* "Apps should be able to run offline when possible" - Apps can use all the same offline features that the web platform offers. Is there any additional work to be done here?
* "Apps should be able to run offline when possible" - Apps can use all the same offline features that the web platform offers. Is there any additional work to be done here?
A: (JA) - I do not see any additional work here. As long as an app that is designed to work offline can we're good. 


* All of the uninstall features seem to be either web-side (launcher page) or WebRT side (OS uninstall support). Is there anything in Firefox UI that needs to be done to support these?
* All of the uninstall features seem to be either web-side (launcher page) or WebRT side (OS uninstall support). Is there anything in Firefox UI that needs to be done to support these?
A: (JA) - Nope


;Recent Changes
;Recent Changes
Line 39: Line 53:
* Removed "use and re-engagement" bit about Home Tab updates when apps aren't loaded, and prompting user while browsing.
* Removed "use and re-engagement" bit about Home Tab updates when apps aren't loaded, and prompting user while browsing.
|Feature overview=* App Discovery
|Feature overview=* App Discovery
** Through the app store.
** Through link to app store on Home tab
** Personalized recommendations in the home tab.
** On the Web.


* App Management
* App Management
** Users can install Apps to Firefox Home and optionally their OS default install locations.
** Users can only install Apps to their OS default install locations.
** Users can uninstall Apps from Firefox Home and/or the OS uninstall mechanism.
** Users can uninstall Apps from the OS uninstall mechanism.
** Users can set individual permissions upon installation, and from the App itself. (CLARIFICATION NEEDED: Is this still a goal for v1?)
** Users can specify how Apps are opened.


;Important Apps Dates:
;Important Apps Dates:
Line 53: Line 63:
*Beta Release: Mar '12
*Beta Release: Mar '12
*GA Release: end Q2
*GA Release: end Q2
|Feature users and use cases=Alice is a desktop Firefox user. She has three paths to discovering Apps in Firefox.  She can click on the Firefox App Store launcher in her Home Tab which loads the Firefox App Store in a new tab or new window (is the store itself an "App"?) and browse and search through our amazing catalog of compelling apps.  She can also browse the "recommended" apps section of Home Tab which will surface a half dozen recommended apps based on her browsing history. Finally, Alice can surf around the Web and be notified by sites about the availability of their Apps.
|Feature users and use cases=;User Stories
 
User: Alice is a desktop Firefox user.  


Alice is in complete control of how and when Apps launch. In addition to explicit launchers, Alice has a variety of ways to indirectly launch an App, for example, from a link on the Web or from within another App. Alice can also customize what kinds of windows her Apps live in.
;Prioritized by (Win7, Mac OS X)
*Alice can install an app natively on Windows 7 from Firefox
*Alice can install an app natively on Mac OS X from Firefox
*Alice can launch an app through native means on a Windows7  desktop
*Alice can launch an app through native means on a Mac OS X  desktop
*Alice can use an app that has an offline mode when there is no connectivity with out loss of data
*Alice can uninstall a natively installed app through native means on Windows 7
*Alice can uninstall a natively installed app through native means on Mac OS X


When Alice doesn't have an internet connection, she can still use any Apps which don't require live connections. She can work offline with confidence that all of her work is being saved locally and will sync when her connection returns.


Alice can easily remove any app at any time.
|Feature dependencies=Platform and Apps work:
|Feature dependencies=Platform and Apps work:
* -webapp mode ({{bug|725408}})
* -webapp mode ({{bug|725408}})
Line 68: Line 85:
|Feature requirements=;Discovery
|Feature requirements=;Discovery
* Firefox App Store launcher in the Home Tab
* Firefox App Store launcher in the Home Tab
* Firefox "Recommended Apps" section of Home Tab
* Mechanism for Web sites to offer an App
* Manual Install button on page that triggers Firefox install flow (CLARIFICATION NEEDED: what does this mean? -DA)


;Install Experience
;Install Experience
* Install prompt is in Firefox chrome
* Install prompt is in Firefox chrome
* Install prompt lists all permissions the App wants, each one with a grant or deny
* Install prompt offers to place a launcher in appropriate OS locations
* Installation occurs when the "Install" button is clicked
* After install has been completed, the user is shown where the app can be found
* After install has been completed, the user is shown where the app can be found
* After install the app is launched (CLARIFICATION NEEDED: which is it, the above or this?)


;Permissions Requirements
; Launch Requirements:
* Permissions settings are per-App
* Native launch works in Windows 7 and Mac OS X
* Permissions re-prompt at App launch as needed
* Global permissions manager
* Apps can register as protocol handlers
* Apps can add "open with" items to Firefox context menu
* Firefox decorates links openable by installed apps
* Apps open in chrome-less windows by default (customizable)
 
;Notification Requirements:
* App launchers must be able to update their appearance


;Offline Requirements:
;Offline Requirements:
Line 96: Line 97:


;Uninstall Requirements:
;Uninstall Requirements:
* Uninstall from launcher page
* Uninstall from system uninstaller, appropriate to the OS
* Uninstall from system uninstaller, appropriate to the OS
* Provide option for per-app data to be retained
 
|Feature non-goals=* Permissions model specific to apps. Apps will use same permissions model as web content in tabs currently does.
|Feature non-goals=; See cut section for more details
* Discovery aside from within the Marketplace
* Apps in the Cloud
* Permissions model specific to apps. Apps will use same permissions model as web content in tabs currently does.
* Notifications of app updates on Home Tab, or prompts while browsing.
* Notifications of app updates on Home Tab, or prompts while browsing.
|Feature functional spec=MOVED FROM REQUIREMENTS - NEEDS CLEANUP.
|Feature functional spec=; Install Use Case - Windows 7
* From Home Tab click on Marketplace link
* Browse to and install an app
* The user is prompted if they are sure they want to install and perhaps some messaging as to where the app will be installed (UX to-do)
* User confirms app installation and app is installed into program files and start menu
* Post install message tells user where the app was installed or the OS can show the user where the app was installed (UX to-do)
 
; Install Use Case - Mac OS X
* From Home Tab click on Marketplace link
* Browse to and install an app
* The user is prompted if they are sure they want to install and perhaps some messaging as to where the app will be installed (UX to-do)
* User confirms app installation and app is installed natively into Apps folder
* Post install message tells user where the app was installed or the OS can show the user where the app was installed (UX to-do)
 
; Launch Use Case - Windows 7
* From Start Menu (or task bar or desktop shortcut) click app
* App launches into a full-screen, chromeless window


;Discovery
; Launch Use Case - Mac OS X
* Firefox App Store launcher in the Home Tab.
* From Apps folder (or desktop or dock shortcut) click app
** Shopping bag icon that pops up a store interface in Home Tab?
* App launches into a full-screen, chromeless window
** Launch a new tab or new page?
* Firefox "Recommended Apps" section of Home Tab.
** Local compare against history/bookmarks for relevant Apps
** Mozilla promoted Apps.
* A mechanism for Web sites to offer an App.
** Automatic Firefox discovery and prompt?
** door hanger?
** infobar?
** Home Tab notification?
** other?
* Manual Install button on page that triggers Firefox install flow (is it even possible to offer an API that requires a user click?


;Install Experience Requirements:
; Re-launch already opened app - Windows 7
* Install prompt is in Firefox chrome.
* From Start Menu (or task bar or desktop shortcut) click app
* Firefox prompt lists all permissions the App wants, each one with a grant or deny.
* App window is refocused
* Install prompt offers to place a launcher in appropriate OS locations
** Start Menu, Desktop, and Taskbar on Windows.
** Dock and Applications dir on Mac
** What ever Linux people expect
* Installation happens when the "Install" button is clicked.
* After install has been completed, the Home Tab loads and the new App launcher animates into view to show the user where she can find it.
** do we automatically launch the app?


;Requirements:
; Re-launch already opened app - Mac OS X
* Permissions settings associated with each App
* From Apps folder (or desktop or dock shortcut) click app
** Firefox context click on launcher?
* App window is refocused
** Firefox context menu when "in app"?
* Permissions prompt at App launch if requested permission had been denied at install time or if a new version of the App requires more permissions.
** never ask again for this permission on startup.
*** can be reversed from Permissions manager for App
* Global Permissions Manager? Like about:permissions but for Apps?
* Apps need to be able to be able to register to handle certain link types
* Apps can add "open with" items to Firefox context menu?
* Firefox badges certain links (by domain?) with a mini launcher icon for opening the link in a particular app rather than the browser window.
* Apps open in chromeless windows by default but that's customizable
** Apps can be set to open in a new window, in a tab, in an App windows fullscreen mode or in Firefox fullscreen mode.


;Requirements:
Use an offline app - Windows 7/Mac OS X
* App launchers need to be able to receive small bits of data and present that to the user in the launcher's space. Think launcher badging and MS Live Tiles.
* User is using an app with an offline mode and there is no connectivity
* Home Tab needs to be able to signal to the user that one of the installed Apps has an update
* Data will be stored locally and synced to app once connectivity is available
* Firefox needs to be able to draw the user's attention to the launchers with updates.
** Is this the apps job to do the Syncing?
*Note: It is up to the app to show UX about offline mode


;Requirements:
; Uninstall - Windows 7
* App cache?
* Open Program and Features
* Local storage?
* Select the app and click "Uninstall"
* online/offline events?
**Uninstall should clear any locally stored app data
* do we already have these things?


;Requirements:
; Uninstall - Mac OS X
* Uninstall from launcher
* Drag the app to the Trash or select to put in the Trash
* Uninstall from system uninstaller
** Uninstall should clear any locally stored app data
** Windows Add/Remove Programs
** Mac drag App launcher to trash?
* Option to keep App data around?
|Feature ux design=Mockups:
|Feature ux design=Mockups:


Line 177: Line 165:
|Feature security notes=bsterne
|Feature security notes=bsterne
}}
}}
;Cut List:
===Overview===
* App Discovery
** Through the app store.
** Personalized recommendations in the home tab.
** On the Web.
* App Management
** Users can install Apps to Firefox Home and optionally their OS default install locations.
** Users can only install Apps to their OS default install locations.
** Users can uninstall Apps from Firefox Home and/or the OS uninstall mechanism.
** Users can set individual permissions upon installation, and from the App itself. (CLARIFICATION NEEDED: Is this still a goal for v1?)
** Users can specify how Apps are opened.
===Requirements===
;Discovery
* Firefox "Recommended Apps" section of Home Tab
* Mechanism for Web sites to offer an App
* Manual Install button on page that triggers Firefox install flow (CLARIFICATION NEEDED: what does this mean? -DA)
;Install Experience
* Install prompt lists all permissions the App wants, each one with a grant or deny
* Install prompt offers to place a launcher in appropriate OS locations
* Installation occurs when the "Install" button is clicked
* After install has been completed, the user is shown where the app can be found
* After install the app is launched (CLARIFICATION NEEDED: which is it, the above or this?)
;Permissions Requirements
* Permissions settings are per-App
* Permissions re-prompt at App launch as needed
* Global permissions manager
* Apps can register as protocol handlers
* Apps can add "open with" items to Firefox context menu
* Firefox decorates links openable by installed apps
* Apps open in chrome-less windows by default (customizable)
;Notification Requirements:
* App launchers must be able to update their appearance
;Uninstall Requirements:
* Uninstall from launcher page
* Provide option for per-app data to be retained
Jarguello
canmove, Confirmed users
457

edits

Retrieved from "https://wiki.mozilla.org/Special:MobileDiff/398942"