Whilst showing and explaining the design prototype I asked my house mates about their thoughts on the following: A student new to University wants to use this as an extension of their social network profile to find other like minded individuals, they would then be presented with invites to events that their new friends are going to.
The following summarises the points raised by my house mates:
The following summarises the points raised by my house mates:
- Privacy issues and fine grain control over features - alerting a whole group of people when you're going to do something could be a problem, there should be more control over who can be alerted.
- Too many friend requests - particularly in a social club setting, could be information overload.
- What is the usable range?
- Vibrate setting - to alert user when in a loud club.
- How will the buttons/user input work?
- Possibly marketed as a male/female watch/braclet.
Our comments to the points raised above:
Privacy issues/fine tuning of features
An example of fine tuning the functions could be choosing from a list of people available who you want to go home with rather then having a list that alerted everyone.
Too many friend requests
A large amount of people in a club could present information overload. How do we show this as efficiently as possible to our users? We could filter people out by categories that show up as a setting on the watch or just have a complete list of friends that the user scrolls through.
What is the usable range?
This would be the bluetooth range 10-100m, a fairly good size for a club or 2 within the local area.
Vibrate setting
This is to alert people especially within a club, just like a phone or pager. Although missed out this was a very valid point as clubs can be noisy and distracting and the best chance of a device like this getting your attention in this setting would be through vibration.
How will the buttons/user input work?
One thing the prototype diagram doesn't clearly explain is the use of buttons or user input. Here most of the user input is done through a touch screen. In the case of settings and events we've added scrollbars to display extra data. Without the use of scrollbars this has the potential to be fiddly if not impossible to use due to the limited amount of space available.
Possibly marketed as a watch/braclet for males and females
This was a nice addition (although part of the asthetics) to the look and feel of the device which wasn't initially thought about.
Privacy issues/fine tuning of features
An example of fine tuning the functions could be choosing from a list of people available who you want to go home with rather then having a list that alerted everyone.
Too many friend requests
A large amount of people in a club could present information overload. How do we show this as efficiently as possible to our users? We could filter people out by categories that show up as a setting on the watch or just have a complete list of friends that the user scrolls through.
What is the usable range?
This would be the bluetooth range 10-100m, a fairly good size for a club or 2 within the local area.
Vibrate setting
This is to alert people especially within a club, just like a phone or pager. Although missed out this was a very valid point as clubs can be noisy and distracting and the best chance of a device like this getting your attention in this setting would be through vibration.
How will the buttons/user input work?
One thing the prototype diagram doesn't clearly explain is the use of buttons or user input. Here most of the user input is done through a touch screen. In the case of settings and events we've added scrollbars to display extra data. Without the use of scrollbars this has the potential to be fiddly if not impossible to use due to the limited amount of space available.
Possibly marketed as a watch/braclet for males and females
This was a nice addition (although part of the asthetics) to the look and feel of the device which wasn't initially thought about.
0 comments:
Post a Comment