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:
- Easy to learn where
to click and how to navigate.
- It is easy to learn how to
navigate because the
labels are self-descriptive.

It provides good affordances to
help the user understand what she
 would see when she clicks on a link.

Cons:

Pros:
Easy to navigate The icons in the
design provide
easy understanding
of the message
that follows.


Cons:

Pros:

Cons:
The user may
Nothing
dangerous can happen.
Cons: inadvertently
delete the offer.
Having a confirmation
dialog will be
helpful.

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

Cons:
However, 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.

Once Bob adds Joe as a contact, Joe can
now search for Bob in his social contacts.
He sees the screen shown here that
indicates Bob’s current location (depending
on what Bob allowed him to view). Joe can
also choose to view historical locations
visited by Bob or Bob’s aggregated information.
On the similar screen on Bob’s application,
where Bob would be viewing Joe’s profile,
Bob would see that the button “View
Aggregated Information” would be disabled since
Joe did not allow Bob to view his aggregated
information.
Suppose that a month has passed since Joe
added Bob to his contact list. Joe can view Bob’s
historical data by clicking on the button called
“View Past Locations”. He would then see this
screen that shows Bob’s locations using markers
on three different maps. These three maps
correspond to a daily, weekly and monthly summary
of Bob’s locations (based on the permissions
that Bob set for Joe).

Pros:


Cons:

The data presented
may be confusing
to some users.
What is the difference
between history
and aggregation?

Also, if the contact
visited the same place
multiple times a
day, would there be
a corresponding
number of
keyhole markers?

Pros:



Cons:
Have
Lacks external
consistency with
other mobile apps.
The user
has to explicitly
search for the
contact to be able to
view location.
Would be better if there
was an
alphabetical list of
contacts
that the user could
scroll through.
Cons:

Pros:

Cannot edit the contact's
information, so nothing irreversible can happen.

Cons:

Pros:
The most important
detail (current location) is
visible in an understandable
manner in a quick glance.

Cons:

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”.

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? What about offers that
can span multiple categories?

Pros:
The wheel analogy of categorization of offers
seems to be useful because users can quickly navigate to the type of
offer they are looking for.


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.

Pros:



Cons:
Users may
If you inadvertently over-share
information, the . The only way
to cancel that is change this
 is by deleting
the contact
relationship. Not very efficient in that respect.
Cons:

Pros:

Options and controls are clearly visible to
the user.

Cons:

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="59b51920a584bfe4-756a83d5-412b4787-bc81a682-3456b38b4292f36ef5515f9d"><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.

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:
Cons:

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.