Versions Compared

Old Version 76

changes.mady.by.user Unknown User (yuhan@mit.edu)

Saved on

compared with

New Version 77

changes.mady.by.user Unknown User (yuhan@mit.edu)

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

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 since Joe
Joe did  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
historical data by clicking on the button called
“View Past Locations”.
He would then see this
screen 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: 
- The map is a good affordance for
location.Also, the map widget is also externally consistent
with other location based apps.

Cons:
- The interface does not speak
users' language. Users might
not know the meaning of
"aggregated information."
.   
- The data presented  may be
confusing to some users.
What is the difference between
history and aggregation?
-* *The interface should provide a
list of friends to be more consistent
with other social apps.

Pros:
- View others location can be done in a single click.
- Auto-complete in the search bar
makes it more efficient for users
to find friends since they don't need to
provide the full name of the contact.

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


The possible mistake
here would be viewing
would be viewing at a wrong
friendundesired friend's
profile. However, this
mistake can be solved
by
clicking on the "Back"
button
on the browser.

Pros:
The most important
detail (current location) is
visible salient 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
 on the tab  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  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 groups the offers and 
seems to be useful because users can 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.
Pros:




Cons:
Users may
inadvertently over-share
information. The only way
to change this
 is by deleting
the contact
relationship
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 displaysdisplays the
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.

Task 4: View aggregate information of social contacts:

...

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="4e7edf806edd2ca5-5ad854b1-4ec4434f-a17ba4b5-bf8eb7ea6cec543946b2a724"><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.


...