Page History

When Joe starts LocaShare,he sees
the home screen shown in the figure.

* Upon clicking the link “view” near
(i), he sees the names of social contacts
that are near his current location. By
clicking on the button “View Contact”,
he can view further details.

* Upon clicking the link “view” near (ii), he
sees the names of people who added
him as a contact. The relationship between
Joe and that person (e.g., Susan) is not
established till Joe also adds Susan as his
social contact. By pressing the button “Set
Permissions”, Joe can add Susan to his
list. If he does not want to share his location
information with Susan, he can choose to
“Deny Request” and Susan would not be
able to track his location (since he will not
appear as her social contact). By selecting
either “Set Permissions” or “Deny Request”,
he can remove the person’s name from this
screen.

* Upon clicking the link “view” near (iii), he sees
a list containing thenames of stores that are
offering discounts or sales in exchange for his
location information.

In all the three cases, he can choose to return back to
the home screen.

Pros:
1. Easy to learn where
to click and how to navigate by
providing texts on the labels.
However, it pays the price
of simplicity. 


Cons:
1. Back button at the bottom is inconsistent 
with other mobile apps. The way
of receiving notification is also
inconsistent  with other
 social apps such as Facebook. 
2. The user interface uses
jargons (social/commercial
contacts and GPS coordinates) 
which makes hard for
users to understand.

Pros:
- Viewing social/commercial
 contact requests can be done
in a single click.

Cons:
- If the list of contacts is long,
users need to scroll down on the long list. 

The error here might be
 viewing the wrong deal
or contact. Users can undo
 this action by pressing the back button.

Pros:
The most essential
capabilities are
directly visible. 
Graphical representation
of what the task entails.

Cons:
- Only numbers
are directly
visible, if you know
that someone has
added you (if they
notify you), you
still have to click the
"view" link and then
acknowledge the
relationship.

- The "view" hyperlink
does not provide
enough 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="b147930117f4f668-9a91993a-4da54396-94b2b7f8-76df89327333ea1427dbd124"><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?

Pros:

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:

No irreversible
action
possible in these
two screens.

Cons:

Pros:

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.