Marketplace/TrustedUIRework: Difference between revisions
Jump to navigation
Jump to search
(→Platform: bugs) |
(added banner) |
||
| (10 intermediate revisions by 3 users not shown) | |||
| Line 1: | Line 1: | ||
{{Marketplace_banner}} | |||
Marketplace Payments is now the only consumer of the Trusted UI. Should we keep it? | Marketplace Payments is now the only consumer of the Trusted UI. Should we keep it? | ||
| Line 16: | Line 17: | ||
=== Platform === | === Platform === | ||
* | * It is difficult to maintain since many code paths within the Trusted UI are unique. | ||
* Multiple bugs keep occurring as the platform evolves. | * Multiple bugs keep occurring as the platform evolves. | ||
* | * Partial list of unexpected bugs: | ||
** https://bugzilla.mozilla.org/show_bug.cgi?id=1105495 | ** https://bugzilla.mozilla.org/show_bug.cgi?id=1105495 | ||
** https://bugzilla.mozilla.org/show_bug.cgi?id=1097928 | |||
** https://bugzilla.mozilla.org/show_bug.cgi?id=1082218 | ** https://bugzilla.mozilla.org/show_bug.cgi?id=1082218 | ||
** https://bugzilla.mozilla.org/show_bug.cgi?id=830358 | ** https://bugzilla.mozilla.org/show_bug.cgi?id=830358 | ||
** https://bugzilla.mozilla.org/show_bug.cgi?id=812663 | ** https://bugzilla.mozilla.org/show_bug.cgi?id=812663 | ||
** https://bugzilla.mozilla.org/show_bug.cgi?id=919833 | |||
** https://bugzilla.mozilla.org/show_bug.cgi?id=834507 | |||
** https://bugzilla.mozilla.org/show_bug.cgi?id=829170 | |||
** https://bugzilla.mozilla.org/show_bug.cgi?id=834871 | |||
* Trusted UI didn't work at all on Tarako phones, meaning that there aren't payments on those phones. | |||
* For developers it is *almost* impossible to debug, it doesn't log to console.log or all those useful places. It's such a pain. | |||
=== UX === | === UX === | ||
| Line 28: | Line 36: | ||
* The small screen is a problem for UX. | * The small screen is a problem for UX. | ||
* It's not obvious what the screen actually indicates to the consumer. | * It's not obvious what the screen actually indicates to the consumer. | ||
* The UX and interactions are different for mobile/desktop, and we need to design our payment system to reflect that. | |||
* The visual design of Trusted UI leaves a lot to be desired. | |||
=== Security === | === Security === | ||
* | * It doesn't fix any of the original security issues it was designed for. | ||
* | ** Spoofability: The Trusted UI opens over the user's home screen but a malicious app could simulate a user's home screen by showing the stock Firefox OS app icons. To the casual user who has not customized their home screen or who is not studying the pixels in details, this spoofed payment window would look the same. | ||
== Solutions == | == Solutions == | ||
What's a better approach? | What's a better approach? | ||
Latest revision as of 02:54, 1 April 2016
.png){kind=small}
The Marketplace has been placed into maintenance mode. It is no longer under active development. You can read complete details here.
Marketplace Payments is now the only consumer of the Trusted UI. Should we keep it?
Originally created in: https://bugzilla.mozilla.org/show_bug.cgi?id=794999
Advantages
What does the Trusted UI provide that is of value?
- A global cookie jar so that information can be re-used across apps. Specifically, when starting an in-app payment from App #1 you have to log in on the first purchase but not on the second purchase. When starting a payment from App #2, you should also not have to log in again.
- A seamless in-app payment flow: the user taps a button, enters a payment window, completes the payment, and is automatically returned to the context of the app.
Problems
What problems does the Trusted UI cause?
Platform
- It is difficult to maintain since many code paths within the Trusted UI are unique.
- Multiple bugs keep occurring as the platform evolves.
- Partial list of unexpected bugs:
- https://bugzilla.mozilla.org/show_bug.cgi?id=1105495
- https://bugzilla.mozilla.org/show_bug.cgi?id=1097928
- https://bugzilla.mozilla.org/show_bug.cgi?id=1082218
- https://bugzilla.mozilla.org/show_bug.cgi?id=830358
- https://bugzilla.mozilla.org/show_bug.cgi?id=812663
- https://bugzilla.mozilla.org/show_bug.cgi?id=919833
- https://bugzilla.mozilla.org/show_bug.cgi?id=834507
- https://bugzilla.mozilla.org/show_bug.cgi?id=829170
- https://bugzilla.mozilla.org/show_bug.cgi?id=834871
- Trusted UI didn't work at all on Tarako phones, meaning that there aren't payments on those phones.
- For developers it is *almost* impossible to debug, it doesn't log to console.log or all those useful places. It's such a pain.
UX
- The small screen is a problem for UX.
- It's not obvious what the screen actually indicates to the consumer.
- The UX and interactions are different for mobile/desktop, and we need to design our payment system to reflect that.
- The visual design of Trusted UI leaves a lot to be desired.
Security
- It doesn't fix any of the original security issues it was designed for.
- Spoofability: The Trusted UI opens over the user's home screen but a malicious app could simulate a user's home screen by showing the stock Firefox OS app icons. To the casual user who has not customized their home screen or who is not studying the pixels in details, this spoofed payment window would look the same.
Solutions
What's a better approach?