Firefox/Features/Web Payments: Difference between revisions

no edit summary
(→‎Development Detail: move DOM to own page)
No edit summary
Line 11: Line 11:
===== Tentative plan for 2018’H2 =====
===== Tentative plan for 2018’H2 =====
* Frontend: Basic card UI implementation. Known dependencies include:
* Frontend: Basic card UI implementation. Known dependencies include:
** 1. (On-going)  UX design reiteration V1.7: Jacqueline is on it. (see also: Web Payment - Basic Card (MVP) design doc.
** 1. (Completed)  UX design reiteration V1.7: Jacqueline. (see also: Web Payment - Basic Card (MVP) design doc.
** 2. Front-end Resources: 3 Engineers  
** 2. Front-end Resources: 3 Engineers  
** 3. (TBConfirmed) Reviewer’s availability: MattN  
** 3. (Confirmed) Reviewer’s availability: MattN  
** 4. (TBConfirmed) No other feature dependency (e.g., Any Lockbox dependency?)
** 4. (Confirmed) No other feature dependency (e.g., Any Lockbox dependency?)
** 5. (TBConfirmed) Compliance for Basic card UI (or that’s only for Payment Handler?)? e.g., PA-DSS by PA-QSA
** 5. (Confirmed) Compliance for Basic card UI (or that’s only for Payment Handler?)? e.g., PA-DSS by PA-QSA


* Platform: Ensure Payment Request APIs “ready to enable” (disable until FE ready) in Q3
* Platform: Ensure Payment Request APIs “ready to enable” (disable until FE ready) in Q3
Line 25: Line 25:
*** IntegrationL requires FE completion to start (e.g., fix bugs during UI integration and verification on merchant website like WooCommerce).
*** IntegrationL requires FE completion to start (e.g., fix bugs during UI integration and verification on merchant website like WooCommerce).


===== Achivement in 2017'H1 =====
===== Achievement in 2017'H1 =====
** (Done) Payment Request API development.
** (Done) Payment Request API development.
** (Done) User research of Payment Request (Basic Card) UX.
** (Done) User research of Payment Request (Basic Card) UX.
Line 36: Line 36:


== Quality Assurance ==
== Quality Assurance ==
* TBD. The pure API development in H1 doesn't require QA involvement (UI level verification). We will have unit/auto test instead.
* TBD. The pure API development in H1 doesn't require QA involvement (UI level verification). We will have unit/autotest instead.


== Project Members ==
== Project Members ==
===== 2018'H1 (Jan.~) =====
* Product: Jeff Griffiths (transition to Cindy Hsiang)
* User Experience: Jacqueline Savory (UX), Erin Pang (VisD)
* User Research: Sharon Bautista
* Front-End Engineering: Justin Dolske, Matthew Noorenberghe (Tech Lead), Jared Wein, Samuel Foster
* Platform Engineering: Marcos Caceres, Peter Saint-Andre
* Program Management: Jean Gong


===== 2017'H2 (Sep.~) =====
===== 2017'H2 (Sep.~) =====
canmove, Confirmed users
1,104

edits