Page History

#1

N/A

‧ Learnability:
1. Different mental model: She attempted
to click on her own profile picture to view
 how Bob could see about him rather than
 clicking on Bob’s page and choose
“My LocaShare”. The user expressed
that since it is how others view my information,
it should be shown in my page instead of others
page.

2. Affordance mismatch: A profile picture has
the affordance to be clickable; however,
our design does not support this function.

3. Misleading arrows/bad affordance: She
was confused by “< My LocaShare” button
and “> Bob’s LocaShare” button. The
direction of the arrows is hard to understand,
the text on the button does not help user to
make the decision as well. Also, the texture
of the button does not make the user feel like
it is a clickable button.

4. Unclear affordance: An empty map in the
editing page makes user think it is a text
box and want to type something in it.

‧ Visibility:
1. User was unable to know the edits were
only applied to a specific friend.

‧ Learnability:
1. Different conceptual model:
User was unable to find the
search bar for adding a
friend since clicking on
“My Friends” does not
make sense ("John is not my
friend at this point").

‧ Learnability:
1. Affordance: User tried clicking
on the box to the left of "Star
Market" as it looks more like
a button than an icon.

User wondered if
it was possible to
create
user-specific
categories.
Also, how to
select multiple
offers at once.

#2

 N/A

‧ Learnability
1. Different mental model: It is more
natural to name the user as “Me”
instead of “Joe”.

2. Inconsistency/different mental
model: We noticed that user habitually
assumed that the picture on the
upper left corner should be me rather
than my friend. Putting user’s profile
picture on the upper right corner is
externally inconsistent with other
social apps.

3. Lack of feedback: The map does not
provide enough feedback about the
coverage of a location. A circle
(with different radius) below the bubble
would help solve this problem. Also,
user was puzzled about what would
happen to the coverage of a location
after choosing “city” or “state”, would
the radius of a location change as well?

 ‧ Efficiency
1. Aggregation: User suggested that the
application should be able to support a
function to hide/show all the charts,
instead of clicking on each chart one
by one in order to hide/show it.

‧  Learnability
1. Different mental model: User
was unable navigate from the
home screen for the “Add John”
task since the user is expecting
an “Add friend +” button on the
home screen. User did not
expect to click on “My friends”
to add a new friend.

2. Lack of feedback:
User was expecting some
feedback would be provided
after adding John, things like
a successful or failure alert.

‧ Learnability
1. Different mental model: User
expected that upon clicking on
the little arrow below “0.4 mi”,
the map/direction to Star
Market would be provided
(since it was directly below
the distance).

2. Affordance: User tried to
click on the "Star" symbol to
see the offers but it was an
icon instead of a button.

‧ Visibility
1. User asked if the user was
not interested in utilizing any
offers right now, is it possible
to provide a way to hide it and
click on "My Deals" to view it
at a later point in time.

#3

 N/A

‧ Learnability
1. Different mental model: User attempted
 to click on his own profile picture to view
 how Bob could see about him rather
 than clicking on Bob’s page and choose
 “My LocaShare”. (Similar thing
 happened to user 1.)

2. Inconsistency: User asked why my profile
 picture shows up when viewing Bob’s
 information. It is externally inconsistent with
 other social apps because they would not
 show your pictures when viewing others page. 

3. Inconsistency: User might expect to have a 
profile page which can be accessible by clicking
on his/her own profile picture just like other
social apps.

‧ Efficiency
1. Aggregation: User asked “If I want to hide
my daily/weekly and monthly stats, do I have
to click "Hide" 3 times?”

‧ Visibiltiy
1. The search bar under the map is not salient.

2. The "neighborhood/city/state" did not
convey the look of radio buttons to the user.

‧ Learnability
1. Inconsistency: User found
the way to add a new friend is
externally inconsistent with the
way to add a new contact on
a mobile phone. On a mobile
phone (contact list), when you
want to add users, you “add”
them instead of “searching”
for them.

2. Unclear affordance: User
attempted to add a friend by
clicking on the “empty box” in
“friends near you”, since it is
intuitive to fill in an empty box
by adding something in it.

‧ Learnability
1. Jargon: The user mentioned
that “Select” sounded rather
ambiguous.

1. User asked “am I
adding Star
Market as one
of my friends?”

2. User 3 asked if the
 "deals functionality"
 could be turned into
 a social experience
 ("I would like to
share my deals with Bob").

#1

‧ Learnability/Efficiency:
1. Multiple accessibility: Liked
that we provide two ways to
access to friends. One is
by clicking on friend’s
picture on the map in the
home screen and the
other way is by clicking
on “My friends.”

‧ Learnability 
1. Not speaking user's   
language:  
"What" is ambiguous. She   
suggested that we should use  
"History" or "Statistics" instead.
 
‧ Efficiency
1. Add multiple people to a 
LocaShare: We should support
adding multiple people to a Loca-
Share. User suggested that this
could be achieved by 
    i. Choosing multiple people 
       while creating a LocaShare.
   ii. Have a "who" tab in the
      setting menu to add people
      and view people who has 
      already been added in the
      LocaShare.

2. LocaShare naming: The app
should allow users to name the 
new LocaShare, since it makes
LocaShares easy to remember.
User also suggested that we
could provide a default name
of a LocaShare, but it should
be fragile.

‧ Learnability
1. Different conceptual model:
I should be able to know all the
LocaShares that I have with Bob,
rather than just showing the
aggregated location sharing 
information.

2. Not speaking user's   
language: 
The sentence "View me as Bob" 
is confusing. 

3. Different conceptual model: 
User tried to click on Bob's  
profile page and find a way to 
view how Bob sees me. (This 
behavior is just the opposite 
from what we faced in first 
iteration). 

‧ Efficiency
1. Too many button clicks:
User felt annoying when she
was informed that there is 
still one more button click 
to finish creating a 
new LocaShare. She 
suggested that the app
should just show the inform
without asking user to click 
on "ok".
 

1. Option to "Duplicate" the
locashares to create them
for other people.

2.Should provide a list of LocaShares.

#2

‧ Learnability  
1. Unclear affordance: User
suggested to have an icon below
the photo to show an affordance
of clicking


‧ Visibility
1. User expressed that she 
would like to know her location
on the map in the home screen.

‧ Learnability 
1. Not speaking user's   
language: Instead of using "What" to
mean statistic charts, we should use
"History" or "Statistics". Also, instead of
using "Where" and "When", use "Location"
and "Time" would be more clear.

2. Inconsistent time display: 
It is bad to use both military time and 
normal time. 

‧ Efficiency
1. Duplicate charts: User suggested to
have only one chart with a bar to control
the frequency instead of having daily,
weekly, and monthly three separate
charts. (Or, it should use different charts
in different context. Restaurants -- how
many times, Location Tracking --
amount of time) 
2. Add multiple people to a  
LocaShare: We should support 
adding multiple people to a Loca- 
Share.
3. Global function: User should be able to
set a global preference which overrides all
the LocaShares. (For example: During this
time, I don't want to be seen by anybody.)

‧ Learnability 
1. Different conceptual model:   
User tried to click on Bob's   
profile page and find a way to  
view how Bob sees me. She says
that since the information is "seen
by Bob," it should not be in my 
profile page.

2. Number of times in the chart
*is confusing: *Say they're at a
restaurant and they get a phone
call. So they exit the restaurant,
complete their phone call and
come back. Does that constitute
two visits? Displaying the
amount of time on the chart
may be more useful.

1. User would be more interested in an
app which shares her exact location all
the time, but she is allowed to specify 
the when to share.

2. User suggested that it may be more 
intuitive to give the user an option of
specifying how long they would like
information to be stored (in number
of days)

3. What if there are multiple restaurants
in a building. How would LocaShare 
identify the location as?

#3

‧ Learnability  
1. Affordance mismatch: 
The bubble-like shape that looks 
like Joe is "saying" something.

‧ Learnability 
1. Inconsistent time display: 
It is bad to use both military time and 
normal time. 

2. Not speaking user's    
language: Instead of using "What" to 
mean statistic charts, we should use 
"History" or "Statistics". 

3. Different mental model: May I add the 
date to "when"? That is, may users are 
allowed to set an expiration date for a 
LocaShare?

4. 

‧ Efficiency
1. Recognition v.s recall: User suggested
that we should provide the locations we 
have already decided to share, they are 
uneditable, but would serve the way to 
remind user where they have already
shared.

2. Recommended location settings:
User said that it would be helpful to show
past statistics of locations I usually share
with others (simplify the need to create
 new locations on the map)

3. Grouping for friends: User suggested
that we should allow 

‧ Visibility 
1. User did not notice that there is a  
"minus" button there allowing her to 
 delete time. 

‧ Learnability  
1. Not speaking user's    
language:   
The sentence "View me as Bob"   
is confusing 

2. Different conceptual model:   
User tried to click on Bob's    
profile page and find a way to   
view how Bob sees me.  

3. Confusing icons: 
User asked why there are two 
pictures when I try to view me as 
Bob?

4. Affordance: Instead of using
charts, user suggested that we
can use a map with multiple locations
indicating the places a person has
been to. And use the size of the
bubble to show how many times
a person has been to the location.