...
Task 2: View real-time location of social contacts:
| Storyboard | Learnability | Efficiency | Safety | Visibility
|
|---|
| 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).
The breadcrumb trail helps the user
navigate back to home screen of the
app or home screen of the social contacts.
| Pros: Once you
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:
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.
| 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:
|
Task 3: View offers and opt-in to create commercial contacts:
| Storyboard | Learnability | Efficiency | Safety | Visibility
|
|---|
 | 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? What about offers that
can span multiple categories?
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 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 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
inadvertently over-share
information. The only way
to change this
is by deleting
the contact
relationship.
| Pros:
Options and controls are clearly visible to
the user.
The wheel structure displays
the major categories very
visiblyThe 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:
|
Task 4: View aggregate information |
of social contacts:
|
Storyboard | Learnability | Efficiency | Safety | Visibility
|
|---|
 | 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:
The user would use the first
two
screens to view the current
location as well, so this task is easy to understand.
Cons:
| Pros:
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:
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).
|
Task 5: Edit social contacts: | Storyboard | Learnability | Efficiency | Safety | Visibility
|
|---|
 | 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="db628578abdf8a97-0168089c-420745fd-910dab75-61c3ad006b302a4df70afdb0"><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.
|
...