Apps/Architecture: Difference between revisions

Apps/Architecture (view source)

32 bytes added , 16 August 2012

Confirmed users

514

edits

@@ Line 98: / Line 98: @@
 |clouserw
 |-
-| rowspan=3 style="background:#DDDDDD" | Payment
+| rowspan=3 style="background:#DDDDDD" |Payment
-| zzz |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
 |[https://docs.google.com/document/d/1NLKbHVPQXa9uvDBC3cfgOD7sIrtIxi0qDoXMQrxcCsI/edit navigator.mozPay API]
 |andreas