Page Comparison

h1. User Experience{toc:outline=true|minLevel=1|indent=20px|maxLevel=3}

This page collects wireframes (mockup screenshots, to varying degrees of detail) that show how human beings might experience interactions with devices and software services that implement parts of the User-Managed Access (UMA) proposition.

h2. Simplified CV Scenario

This set of wireframes was originally developed for the UMA webinar held on 29 Jan 2010. to map Beprotocol suredetails to user experience realities. review theThe [webinar overview slides |http://kantarainitiative.org/confluence/download/attachments/37751312/uma-webinar-2010-01-29.pdf], which explain the scenario setup and how often eachthe of thevarious interactions isare performed (most are one-time-only, and most of setup; the rest are optional).

Click the image to see the wireframes.  (There are "click-throughs" on the screens to give you a simulated user experience; the instructions on the right-hand side indicate where most of the links are.)

{html}
<a href="http://kantarainitiative.org/confluence/download/attachments/37751312/UMA_CV_wireframeV7.pdf"><img src="http://kantarainitiative.org/confluence/download/attachments/41026357/simple-cv-scenario-intro.png" width="500750"></a>
{html}

h2. Setting Policies and Terms

This is a single screen that was developed early in the ProtectServe/UMA process to explore policies and negotiation terms that might be interesting to an authorizing user.  It is discussed [herefurther in the [Issues section|http://kantarainitiative.org/confluence/display/uma/UMA+Scenarios+and+Use+Cases#UMAScenariosandUseCases-Issue%3AHowTermscanbeMet] of the Scenarios and Use Cases document.


!UMA Scenarios and Use Cases^copmonkey-policy.png!

h2. Real-Time Consent Gathered Out-of-Band

If some sort of "ask me for consent" option is presented to a user as shown in the above sections, in many cases the consent will need to be gathered in an out-of-band fashion.  Mobile devices are popular for such a purpose.  This set of wireframes was developed to explore how consent might be gathered from an authorizing user given that a requester has approached a host at a time when the user is not logged in to either of them.  (Some reasons for needing real-time consent are discussed in the [Requester 
@@most of this page TBS -- stay tunedIdentification section|http://kantarainitiative.org/confluence/display/uma/terms_id_scenario] of the Scenarios and Use Cases document.)

Click the image to see the wireframes.

{html}
<a href="http://kantarainitiative.org/confluence/download/attachments/41026357/UMA_iPhoneApps2.pdf"><img src="http://kantarainitiative.org/confluence/download/attachments/41026357/mobile-wireframes-intro.png" width="300"></a>
{html}