Apps/Architecture: Difference between revisions

Line 68: Line 68:
| rowspan=3 style="background:#DDDDDD" |We will offer our developers (1) a centralized way to price and manage paid Apps, including integration with multiple billing providers, as needed; (2) a unified Javascipt DOM API to facilitate In-app payments from Users for digital goods within Apps. We will offer users (1) a unified, trustworthy experience of purchasing and seeking refunds for paid Apps; (2) a consistent, trustworthy experience of making In-App payments  
| rowspan=3 style="background:#DDDDDD" |We will offer our developers (1) a centralized way to price and manage paid Apps, including integration with multiple billing providers, as needed; (2) a unified Javascipt DOM API to facilitate In-app payments from Users for digital goods within Apps. We will offer users (1) a unified, trustworthy experience of purchasing and seeking refunds for paid Apps; (2) a consistent, trustworthy experience of making In-App payments  
| style="background:#DDDDDD" | [https://docs.google.com/document/d/1NLKbHVPQXa9uvDBC3cfgOD7sIrtIxi0qDoXMQrxcCsI/edit navigator.mozPay API]
| style="background:#DDDDDD" | [https://docs.google.com/document/d/1NLKbHVPQXa9uvDBC3cfgOD7sIrtIxi0qDoXMQrxcCsI/edit navigator.mozPay API]
| style="background:#DDDDDD" | andreas
| style="background:#DDDDDD" | benadida
| style="background:#DDDDDD" | not sure
| style="background:#DDDDDD" | not sure
|-
|-
Line 76: Line 76:
|-
|-
| style="background:#DDDDDD" | [https://mozilla.com/ In-app payment specification]
| style="background:#DDDDDD" | [https://mozilla.com/ In-app payment specification]
| style="background:#DDDDDD" | kumar
| style="background:#DDDDDD" | benadida
| style="background:#DDDDDD" | kumar
| style="background:#DDDDDD" | kumar
|-
|-
Confirmed users
514

edits