search

dimmyvi / tigress-requirements

Other
0 stars 3 forks source link

Arbitrary message channel review needs to be updated #20

Closed bslassey closed 2 years ago

bslassey commented 2 years ago

In the existing solutions review for arbitrary message channels

The Provisioning Information MAY be sent from Sender to Receiver over an arbitrary messaging channel, but that would not provide a good user experience. Users MAY need to copy and paste the Provisioning Information, or need a special application to handle some new file type. This violates (Req-SmoothUX). If multiple round trips were required the user would need to manually managing multiple payloads of Provisioning Information. This would be very hard for anyone non technical and greatly limit adoption. This violates (Req-NontechnicalUX).

First, this references the two UX requirements that we removed (and besides that, I don't think it is the case that copy and pasting would be required). The one bit that remains is that provisioning may require multiple round trips. That seems like an assumption that we're making that should be documented and substantiated.

castiz commented 2 years ago

Closing this issue since Brad put up a PR and it has merged.