Page History

Joe starts from the home screen and clicks on the
 tab “Commercial Contacts”. He is then taken to the
screen shown here that can be considered the “Home Screen” to handle his commercial contacts. Here, he can view various categories of products on a wheel.

Since Joe is at a ski resort and wants to buy some gear,
he selects the wedge titled “Sporting Goods”
and is taken to the next screen that shows
him the list of stores selling sporting goods
and having offers.

He can then click on the company providing
the offers and see the details of the offers.
To help Joe understand the exact information
he would be sharing, LocaShare displays his
current information as an example.

Joe can choose to accept or delete the offer
by pressing the “Accept” or “Delete” buttons
respectively.
 
Once he accepts an offer, he would see a
summary of the information he is about
to share with Rei on the screen. He can
choose to create a category in which to
save Rei as a contact. He finishes the
process by pressing the “Save Contact”
button or cancel the offer by clicking “Cancel”.

The breadcrumb trail helps the user
navigate back to home screen of the app or home screen of the commercial contacts.

Pros:
- Before confirming the relationship, the design gives feedback to the user about the location that will be shared.


Cons:
- The numbers in circles could be misleading. Are they based on the number of offers in that category?

- Would the wheel rotate when swiped? That would be the user's model of such a construct.
If the wheel is intended to be stationary, a list mechanism may be far easier to learn. Also,
 what do the size of the wedges mean?

- What does the wheel chart in the third slide mean? Users do not have default sharing settings in this design and the user has not started sharing with Rei yet. The label should be modified to say "sample
information"

Pros:
- The wheel analogy groups the offers and  allows users to quickly navigate to the type of offer they are looking for. This avoid users from scrolling down on a long list to find a specific offer. 


Cons:
- Have to go through four screens to establish the commercial contact relationship.

- Having a search mechanism will be helpful
since search is quicker than trying to locate a type of offer that does not neatly fit into any
pre-defined category.

Users may
inadvertently over-share
information. The only way to
change this is by deleting the contact relationship.

Errors might also occur by clicking on "Accept" or 
"Delete" too quickly. A confirmation
alert should be used here.

Pros:
The wheel structure displays the
major categories very 
visibly.

Helpful information is presented in an
externally consistent
manner (e.g., distance from the user's location
to the store. this is
similar to how Google Maps
displays the location).
 

Cons:

- "Clicks to view" does not provide helpful information scent.

Since Alice wants to view Joe’s aggregate information,
she first searches for Joe on her “Home Screen”
for social contacts. She then sees Joe’s profile as
seen in this sketch. At a glance, she can see that he
is near Sunday River and so she is relived that he
reached the resort safe and sound. When she clicks
on “View Aggregated Information”, she sees the
following screen. She can see a summary of Joe’s
location on a daily, weekly and monthly basis. Instead
of a map view that showed Bob’s locations using
markers, in this aggregated view, Alice can see a pie
chart/wheel showing the amount of time Joe spent at
various places.
Alice can choose to drill down and get additional
details by selecting a wedge from the wheel. Suppose
 that she selected the category “Campground”
(shown as a shaded region), she can see a list of
places related to “Campground” that Joe has been
to and the amount of time he spent at each place.

The breadcrumb trail helps the user navigate back to
home screen of the app or home screen of the social contacts.

Pros:
- Good affordance provided by the charts
which implicitly represent aggregate information.


Cons:
- The graphs do not really convey interesting 
information. May be helpful to show the
information on the fourth screen on hover
(instead of clicking and going  to another screen). 

Pros:
- The charts summarize complex aggregate information. this is an efficient way to
represent data.
Cons:

- Have to go through three
screens to view the
interested
data. May be helpful to
have hovering mechanisms that
display necessary information to the
user without the need
to navigate through
so many screens.
Cons:

Pros:

- No irreversible change
can be done in this viewing task.
Cons:

Pros:
- The charts are relatively salient users. 

Cons:
The word "view" does not provide
helpful information scent.

Since Joe wants to modify the location permissions
for Bob, he first searches for Bob on the “Home
Screen” for social contacts. After he comes to
Bob’s profile, he clicks on Bob’s icon/photo and
comes to this screen. Here he view the amount
and type of information that Bob can view about
<ac:structured-macro ac:name="unmigrated-wiki-markup" ac:schema-version="1" ac:macro-id="2937dd50e73706a9-8b1f628d-43fd4246-802f8d73-70e8b7b65643ad26b2d56b90"><ac:plain-text-body><![CDATA[him. [Note: Suppose that during the trip Joe
]]></ac:plain-text-body></ac:structured-macro>
allowed Bob to view his aggregated information.]
Joe can see that Bob can see his current location
as the lat/long in Cambridge, MA (his current
location). He also sees the pie chart/wheel that
describes the categorization of places that Bob
was able to view about him. He can now choose
to modify the permissions by clicking on the button
called “Modify Permissions” or can choose to
return by clicking “Cancel”. Once he clicks “Modify
Permissions”, he taken to the permissions sketch
described in task 1.

The breadcrumb trail helps the user
navigate back to home screen of the app
or home screen of the social contacts.

Pros:
Cons:

The task is not very easy to
learn in these two
slides, since the bulk of the editing
happens in the permissions screen.

He "clicks on Bob's icon/photo and
comes to this screen". How will users
figure that out on their own?

Interface contains jargon. What does
"GPS coordinates" mean?

Pros:
- Can edit permissions
using a single button click.

- Cons:

May be helpful to have a
"Cancel
This Option" button beside the
specific/aggregate information
display. That way, the user
does not have to go to the permissions
screen to cancel
aggregation option (for example).

- No irreversible
action
possible in these
two screens.

Pros:
- You can view all the
information (both detailed and
aggregated)
that
Bob can see displayed on the screen.

Cons:

The data that the
social contact
(user's
friend, for example)
can see is very visible
and easy to understand.

The control for editing
task is not visible at all.

Since this task started with Joe seeing an offer from Rei,
he is led to this sketch by clicking on Rei’s icon in the
screen described in task 3 (that shows the two offers
provided by Rei). In this screen, Joe can view the
 current and aggregate information that Rei is able to
view about Joe. Since a commercial contact is not
editable by Joe (it was tied to the specific offer), he
can only choose to continue sharing the information
 or delete the contact. If he happens to accept
multiple offers from Rei (that require different types
and/or amounts of location information), this screen
would show a summary of entire information set
 that he is sharing with that one store. In that case,
clicking on “Delete Contact” will stop Rei from accessing
any of the pieces of information it was able to access
previously.

The breadcrumb trail helps the user
navigate back to home screen of the app
or home screen of the commercial contacts.

Pros:
- The wheel chart design is internally consistent with that of task 5.

Cons:

- The task is not very easy to
learn in these two slidesthis slide,
since the bulk of the editing happens in the permissions
 screen.
- The button labels are confusing because the
 "delete contact" and "cancel" seem to convey the same meaning.

Pros:
- All the necessary information is present
on the screen. Therefore,
the user does not have to
navigate between screens or scroll to view additional details.

Cons:
- May be helpful to have a
"Cancel This
Option" button beside the
specific/aggregate information
display. That way, the user does
not have to go to the
permissions screen to cancel
aggregation option (for example). Pros:

Cons:
- What if the user wants to
share a subset of
information with Rei? This
design describes an
all-or-nothing approach.

Pros:
- Necessary information is visible on the screen.


Cons:
- The data that the social
contact (Rei, for
example) can see is
very visible and easy to understand .