ME310Nokia Stanford Meetings

From NRCwikis

 ME310 Nokia

 Stanford Meetings

 Finland Meetings

 Stanford Files

 Finland Files

[edit] Mon - Mar 5, 2007

• Finnish Video
  • Less ads or not?
  • click ads off in the video half way through
  • chose language? in video demo
  • personalized ads
• models being finished
• have someone be in charge of travel.
• things to work on
  • what the value
  • target group
  • plan what to do next quarter
• set a goals for the trip to finland
  • what to have finished by then
  • what to accomplish during the trip

[edit] Tues - Feb 20, 2007

STANFORD MEETING WITH TEACHING TEAM (SGM)

Decide if you are going to do VG on objects or images/places

Images/places

• Tracking Map - follow a sequence of photos (several little photos) that can lead you anywhere
• Potential Problem with places is that you have to be in the exact location as before to see graffiti
  • answer? maybe use a video device to scan around
• assume technology - in an object in the image gets moved, software can locate it if the move is llittle or not display VG is move is large
  • Carillation?
  • Software that rebuilds 2-D images into 3-D images
• Focus on user input
  • Someone comes in and can use system/experience that feels real

• LOOK INTO: Drawball.com - public graffiti
  • public interaction
  • what is outcome/going to see

• Idea: Chair - test compass/angle
  • sit with laptop and spin
  • view graffiti scrolling across the screen
  • frames/pictures

• LOOK INTO: Bob Smith's Ephisy?
  • many photos stiched together

• Heads-up display systems
  • Helicopters
• Dave Cannon - put that there project
  • Disabled use robots ... tell them what to do through the use of a laser

• LOOK INTO: Crossbow technologies
  • technology that tells orientations

[edit] Mon - Feb 19, 2007

VIDEO CONFERENCE WITH STANFORD/FINLAND

Video of Ideas for Virtual Graf.

• Pinpoint Location
  • Camera
  • Barcode
  • RFID
  • Bluetooth
  • Wireless
  • New Tech?
• Display
  • Screen
    • Transparent
    • Camera
    • Tags
• Security - Tags in/out of a house
• Input
  • Stylis - writing
  • Motion Detector
    • Accelerometers
      • Nokia Sport
    • Gyroscope
    • Mosquito Game on Phone (Tech?/Software?)
  • Fingers - Type (Keyboard)
  • E-beam
  • Laser
  • Infrared
  • Mouse
  • Touch Screen
  • Voice

Prototyping Steps

• Location-GPS To Spot
• Picture with tags and Virt Graf
  • 360 Deg pics (8 pics in a circle)
  • compass
• Nokia Hot Spots
  • every 15 m
  • Similar to WIFI
    • Display names
    • Location Base
  • Button to pick spot - tag
  • Local positioning sys

[edit] We - Feb 14, 2007

• Next direction
  • Go back through the scenarios and storyboards that we generated before
  • RFID
  • Barcodes
• Virtual Graffiti
  • Detection of object / Location
    • RFID, Barcodes, Image Recognition to recognize objects
    • GPS/RFID to recognize location
    • Dicrection recognition: Image recognition, compass, GPS that detects direction
  • Input
    • Gesture recognition: accelerometers
    • Tablet stylus
    • Use camera to take a photo of the image to write the comments on to.
    • Stores can upload data to add to these walls
  • Output
    • Comments on the object/location appear augmented on the screen
    • Comments are augmented on physical walls
    • Preprogrammed images of objects/locations
• Other Ideas
  • Camera tilted at x degrees so that taking photos seem more natural

[edit] Tu - Feb 13, 2007

FunKtional Prototype Review: Mark, Vic, Alissa, Micah, David

• Teaching team liked that we were tackling the technological aspect of the problem
• They also liked that we did user testing with random subjects
• They were concerned about the novelty of the idea.

• A question to ask ourselves: What is the real value of the service that we are providing? What incentives can we provide for users to want to use our service? It might be something subtle like a comment ranking system, a slightly easier interface, or have the service be useful for a more specific usage scenario.
• How about a user leaving comments through a multiple choice interface.

[edit] Feb 6 to Feb 12

Prototyped a web-based Web 2.0 commenting service on the N800. The webpages accessed a mySQL database to manage the information. Tried to prototype a Bluetooth mobile 2.0 commenting service using python on the N70 phone. This involved:

1. Extracting contact informatin from the phone and storing it in a file (succeeded)
2. Sending this file to the computer (succeeded)
3. Extracting information from the file and using it to select comments from a mySQL database (did not try)
4. Sending information from the computer to the phone (We couldn't find enough python/bluetooth support to accomplish this)
5. Extracting information from a file sent from the computer and displaying it on the phone (succeeded)

Teemu and Eric worked on a prototype of the form factor of the device.

[edit] Th - Feb 1, 2007

• Meeting with Nokia Design, Calabasas

• Raphael - in person at Nokia PA
• Andrew, pd , 12 years at nokia
• Rich?, id, 5 years
• Tom, id, 10 years

• friend's feed + grafiti

• things like friend finder out there - nokia sense... personal profiles in proximity

• nice tie in with very human technology abstract in friend's feed + grafiti

• bob having to look down at little wrist watch all the time

• how to make tagging more rich, seamless or seamfull (fun)

• mix friend newspaper with online news .. quite provocative

• everyday, make coffee, bbc news, flickr, email ... combine? ... my news in addition to news in rest of the world

• could trust your instincts or go with what people like in survey

• using dynamic address book as core... but inclusive of grafitti and friend's feed

• need simple, easy way of digesting data (awkward in darkhorse)

• could add news feed for example through dynamic address book

• dynamic address book could be platform of other experiences, newspaper and grafiti are extensions of dynamic nature of address book... start to add contextual and experiential and environmental information... becomes less primitive

• subtleties of human communication.. constantly managing and shifting our communication

• physical act for bob's experience was obstrusive... looking at watch instead of having dinner with me... looking at watch is usually a fleeting gesture... people don't like when you are looking at watches while talking to them.. they think you are bored

• not just interaction or web 2.0 project.. changes object.. very exciting

• address book is often the first place people look for things

• many things we carry with us, fundamental restrictions on display size of watch... headset displays in glasses, devices the size of a cigarette case or a wallet, notebook, etc.

• gesture in looking at a watch crossing your body, closes yourself off

• based on interaction, choose best device... social implications of the objects you carry... perhaps a small notebook with a display

• when a person goes to the bathroom at a restaurant, the other person often looks at their phone.. source of information

• lifesize is a compelling idea.. full size display not that interesting.. brian eno did installation of his grandparents talking with speakers at the heights of their mouths

• truly mobile lifesize communication

• sometimes you don't need to see people to communicate... feel close if you are sharing experiences.. watching something remotely at exactly the same time... consuming media together is a way of feeling closer

• how to interact with virtual grafitti... make them meaningful.. markers you could find on objects.. touch phones... very interested to see how it would work as an interaction experience

• always come back to people

• monty python... think of idea.. then think, how to make it sillier.. even sillier, then another people says how to make it even sillier... change sillier to simpler.. good direction for project.. keep making it simpler and refining it for the users

• they want whichever deliverables are the most convicing... they use all kinds of deliverables themselves

[edit] Tue - Jan 30, 2007

Team meeting
We rated our ideas based on coolness, novelty, potential for biggness Our favorite ideas are 1. the Virtual Graffiti 2. Friends Newspaper

SGM

• New Friend finder: touching phones to connect could be a gesture
• go into details of scenarios
• Profiles: too much info if get all profiles
• Interface: intent is important. you want to make sure that the user has the intent to do something before the device automatically does it.
• touching phones to transfer info. it’s a gesture. you could use accelerometer data to detect it.
• find smart devices and live around them
• how do you tag stuff that’s not already tagged. how do you tell what you are tagging. how do you know if you are tagging the monitor, the computer, the desk the computer is on, the room the computer is in, etc.
• graffiti that dies. if people don’t access it enough, the comment/graffiti dies.
• common theme: how are we going to tag things. how are we going to put tags on restaurants, physical objects.
• 8meme tags (5 to 10 years ago).
• future vision, assuming things are going to exist in the future, what need does this development address? what if these developments don’t happen? what are people going to do until these developments happen? maybe we approach the same need from a different perspective.
• tagging is a common tag
• the teaching team can help us with testing if the tagging gesture works.
• virtual tagging ideas: have a projector/ camera system that keeps track of pen movement. use glasses that will project the graffiti.
• once we pick a scenario: research more in depth, buy, test, detailed scenario

[edit] Mon - Jan 29, 2007

Meeting with Finnish Team
People:BDER, Laura, Teemu

1. We talked about an approach for the next prototype: putting services on existing mobile devices and figure out what the physical needs are.
2. Survey: ww w.surveymonkey.com/home.asp
   • Finnish team will update the survey. Both teams will send it out to many people.
3. Committees for various tasks
   • Interface technology: Eric and Teemu
   • Physical circuits that we could build: Ruka
   • Continuing with putting services on existing devices: Danielle, Laura, Lasse, Bhargav

[edit] Sun - Jan 28, 2007

Created Survey on www.surveymonkey.com/

[edit] Thu - Jan 25, 2007

Shared the storyboard drawings that we made for the list of Mobile 2.0 services that we brainstormed on Nov 24, 2007.

[edit] Wed - Jan 24, 2007

List of existing Web 2.0 services:

• Facebook
• MySpace
• Online common high score posting
• Wikipedia
• Blogs
• Walls (Facebook, etc)
• (Restaurant/Product) Reviews (rottentomatoes)
• Flicker
• Wikis
• ebay
• craigslist
• del.icio.us
• dodgeball
• Adsense
• Amazon
• helio phone
• friend map
• outlook calendar

Brainstorming Mobile Web 2.0 Services:

• Bubble/Folksonomy
  • photos
• Mobile Dating
• Searches of your friends info
  • personal profiles
  • comments
  • whatever info they post (recipe)
• Friend prioritized searches
• Posting user generated comments on objects (virtual walls on objects) (walls could be liked if they are related)
• Blogs/walls for news on news paper (friends comments are ranked higher)
• Friends history/post become or integrate into news
• Dating / Friends
  • Locating existing friends
  • Finding new friends based on shared interests
  • Friend profile
  • Exchanging personal history
  • Finding friends of friends
• Spontaneous note taking
  • for sharing ideas with people who aren’t there
  • for storing and organizing the data
• Content/news that comes up based on location or time

Mobile Web 2.0 Ideas to Storyboard/Draw:

1. Profile for friends who are in your address book (Danielle)
   • Simplified version of myspace
   • Your contacts have control over their contact info on your phone.
   • Seemless integration of facebook/myspace with your address book.
2. Shows profiles of people who are close to you (Danielle)
3. New friend finder (Eric)
   • people upload their profile/preferences/interests
   • when there is a match of interests the device alerts
   • It could also show profiles
4. News feed about what friends have been upto (like facebook) (Ruka)
   • Friends newspaper
   • It could filter according to your location and time
   • could be integrated into news from society
5. Automattically tagging mobile comments/blogs/photos (Bhargav)
   • tags your comments/blogs according to location and time
   • (restaurant input)
   • spontaneous comments
6. Manually taggin info (Bhargav)
7. Device automatically giving you the info that you want depending on time, location, habits, schedule, etc. (Eric)
   • ex. restaurant watch prototype
8. Posting user generated comments on object (Eric)
   • things have rfid tags. and each tagged object has a virtual wall where people can make comments about it.
   • maybe walls of related objects can be linked
9. The news on newspaper have walls/blogs. comments from friends are prioritized. (Ruka)

[edit] Tue - Jan 23, 2006

[edit] Meeting at Nokia

2pm Meeting with Nokia - Agenda

• Stanford Dark Horse Prototype
  • Video recap of testing
  • Discussion
    • Results
    • Advantages/Disadvantages
  • Human Interface upgrade
• Finland Dark Horse Prototype
  • Window Shopping
    • Theatre Tickets
    • Window Shopping
  • Discussion
    • Results
    • Advantages/Disadvantages
• Future schedule/Recommendations
  • Integration of Stanford/Finland prototypes

Meeting Notes --

• voice regocnition in / text out
• person much more likely to leave a comment on a resaturant if you say it than type it -- not any more obtrusive than talking on the phone
• location-based smart voice recognition... hears 'curry' rather than 'carry' in a restaurant
• make new device to be more suited for our scenario/content
• ipod shuffle -- wear on shirt, offers just what needs to be there
• device as pen
• Vidya will lend us nokia phones to prototype on and help us put flash movies on them
• device hardware constraints that prevent user from using sw well --- then we make a physical device to solve these constraints
• next steps:
  • week 1. list of services
  • week 2. build ui of devices on phones
  • week 3. user testing

• wrist-band requires two hands
• we should test web2.0 on existing devices rather than on new device.
  • why not use the devices that people use right now? why not add serves to the existing mobile device?
• to introduce a new physical device rather than using an existing device, there has to be a good enough reason.
• incentive to buy new device: I have a mobile phone but, I still need this new device.
• could tackle an interface problem for inputting information in new phones. what’s the optimal interface? for leaving comments?
• voice input to text output
• voice recognition isn’t perfect so has to modify it somehow.

• what physical problems are going to arise if we provide a web 2.0 service?

with the wrist-band? –

• test web 2.0 concepts on current existing devices. the web 2.0 concepts will most likely work on current existing devices, but there will most likely be physical problems that we can tackle.
• we can chose what concept to persue by picking the one that introduces a physical problem.
• use flash webpages on the phone for the prototype
• we could also prototype on pdas
• Bluetooth gps for phones – vidya

• what device do you desire?
  • mind-reader (too futuristic)
  • wearable phone
  • automatic address book adder (too software)
  • connect speaker to neck/vocal chord

• give a device someone and ask what else to do you want in it?
  • some people will have trouble coming up with new stuff
  • then give then specific applications and ask them about it. ask more specific questions rather than just giving them a phone.

• we could try out web 2.0 applications on some high tech devices that nokia gives us.

• design user study so that we get information about physical problems/needs

• Formulate user test questions to answer physical needs
• Service Application, what web 2.0 applications are the most important for users
• questionnaire for Stanford students with prizes to figure out what the the most important applications?
• bottom line is we will be questioned on what service we are providing. then after that the questions is rather the device matches the services.

[edit] Meeting with Teacing Team

Darkhorse prototype [
people: mark, vic, micah, david [br>

What we presented

• why is it web 2.0?
• cell phone is hidden in pocket, but the watch is aways on the watch
• interface: tilt sensor
• video
• what we learned
  • comments from friends are good
  • don’t have to take watch out of pocket.
  • not a big advantage over having a mobile phone. Output, both devices requires the use of a hand. Input, requires use of both hands rather than one hand.
• next approach
• Finland prototype

Feedback (Key Points):

• Finnish Prototype
  • Very interesting vision of the future
  • Big assumption that the world will have screens everywhere that will be compatable with our device.
  • Might be too futuristic to be able to make it into a meaningful prototype by the end of the year
• Sanford Prototype
  • Vic: Not physical enough. Don't see how we will be able to incorporate enough physical elements with our current approach.
  • The service itself is nothing new, need to identify what physical needs arise when we make Web 2.0 mobile

Feedback:

• modo – proximity based pda
• Qcad
• barcode in magazines and advertisements
• our plan for our next prototype
  • Mark: what’s going to be the instant gratification for our device? the restaurant review doesn’t provide instant gratification.
• ruka: by imagining new devices for new services, we are identifying a “physical solution” before we identify the “physical need”
• we should brainstorm service
• mark: how do we explore what’s the ideal input/output method?
• micah: new successful ideas aren’t always totally new ideas.
• laptop is a portable device that provides lots of web 2.0. the important thing is to address the interface need that prevent people from using existing web 2.0 services on existing devices everywhere.
• one-millimeter guy.
• I want the technology to look good. unintrusive device.
• concern: what’s the turn around time for creating a flash/web interface. if we try to do it in one week then we might need to costrain people in the scenarios.
• we can use existing services on existing devices like blackberries.
• address requirements in terms of very human and web 2.0.

[edit] Meeting with Bill Cockayne

Bill Cockayne is an expert in evisioning the future

• design.phyllips.com : futuristic communication/technology ideas
• might get more useful feedback if we are testing where users are purposely trying to point out bad things about the device.
• who are we targeting?
  • age ranges -18, 18-34, 30-50, 50-
  • if we are targeting 18-34 for something in 10 years, then we have to think about people 8-24.
  • different age ranges have different expectations for devices and means for communication
• what are the carriers sending as the next set of features?
• whats the best source for looking at future predictions about hardware services?
  • forster research
  • institute of the future
  • look up future of mobile technology
  • rcr news (radio and communication c_____)
  • everyone has been wrong about what has been coming
• devices that kids use
  • leap frog (company called Leap)
  • Fly pen (Bob smith has something similar)
• move-that-there: look it up
  • dj set – at MIT media labs – touched base interface
• virtex: cyber gloves
• interface things that kids do
• businesses should add toy development, so that they can influence kids to buy their products in the future.
• apple future videos
• nokia, snowball video
• show a video of how its supposed to be used. then give the audience a physical prototype and have them use it.
• love_getty: Japanese
• we could do some needfinding at an elementary school.
• ruka: continuously provide information that may not be relevant. let humans do the filtering of information.
• BING
• what were shocking to the teachers?
• have the right information find me?
• positional data in terms of its position relative to other devices
• fmri: reading minds
• bill cockayne inventions: Modo
• in the past there wasn’t the band width and storage space that we have today. what will people have in the future that we don’t have now?
• start every meeting with a video

[edit] Jan 22, 2007

9am Videoconference with Finland

Finnish team darkhorse

• connect with tv with keychain device

• bring up your desktop on tv in store

• bring up screen on back of trainseat

• buy concert tickets by connecting with poster

[edit] Jan 21, 2007

Prototype Testing on University Ave. with Bob Members: BDER, Bob

We went on University Ave to test our prototype. The we prototype the idea of having a portable device that would intelligently display information that would be relevant to the user in his/her situation. The user will also be able to write spontaneous comments that are tagged automatically and uploaded to a server. For the prototype we specifically tested the scenario of finding a restaurant and dining at a restaurant. Scenario:

1. User starts at Borders
   • Device displays genera info(name, type of store, traffic, friend traffic, rating, number of comments)
   • Next displays comments about Borders from three friends
2. User walks along Univ Av and stops at Siam Royale
   • Device display genearl info
   • Device displays two comments
3. User continues on Univ Av. and stops at the Italian Restaurant
   • Device displays general info
4. Since the info on the Italian Restaurant is bad, user decides to go back to Siam Royale
5. Inside Siam Royale
   • Device displays comments related to the menu
   • After finnishing the meal user writes comment about the meal

'What was learned?

• Useful because it automatically displays relevant information without the user having to search
• Add more stuff to this list

[edit] Jan 20, 2007

Meeting to design and built dark horse prototype
People: BDER Bob Smith

• Does the device intelligently decides what the user most likely wants to see, or does the user search for information?
  • Intelligently selected content: Some possiblilities include, the device knowing the user's schedule, lifestyle, habits, preferences, current location, current time to decide what to display. This requires less work for the user.
  • Intelligent searching: The user can chose to search for information. The search could incorporate curent user information to make it intelligent. User has more control over what they see this way.

• For the prototype we are testing intelligently automatically selected content in the scenario of eating at a restaurant.

• Interface Ideas
• accelerometer
• tip sensor, only shows messages when you are looking at it. flick wrist to flip through messages

• Created and uploaded the comments that will be on the device when testing it on University Ave.

[edit] Jan 19, 2007

Location: Nokia
Members: Ramin, Vidya, Maryanna,Stanford Team, Laura, Teemu
Maryanna: Computer Interaction Research

Agenda

1. Report feedback
2. Summary of 2006 Progress
3. Current dark horse work
   1. Web 2.0 approach
   2. Story boarding
   3. Vision for the future
   4. Ideas
   5. Prototyping
4. Discussion

Summary of Feedback

• The new Web 2.0 approach is more inline with current trends and more tangible, but don't forget the work we did in the Fall with environment/context sharing.
• Visualize our progress by creating a flow chart. Make a timeline with milestones.
• Eventually publish the ME310 method with Nokia
• Contact Nokia for help with user studies
• Storyboarding a good exercise. Could do it more and get feedback from external sourcese.
• How is technology used in each part of our scenarios?

Meeting Notes

• Ramin read, sent to nokia design
  • which of the designs in the report are we persuing?
  • what’s new and different about the ideas in our report?
• Stanford team taking a web 2.0 approach.
• Stanford team looked at abstract bullet points and discussed (technology, concepts)
• Example of story boards (eric’s) - feedback great
• vidya likes new approach. our new scenarios are more realistic and more on the line with current development.
• another scenario: go to a museum see a painting, theres a prof that likes painting in same area
• one dimensional approach that is for one service. to multidimensional approach where many services.
• python chat client with GPS data for prototype?
• speed research: scott playmer(?): pick a number of different objects, like at a garage sale. different objects on a vertical axis and a the price people are willing to pay for it one a horizontal axis. to play with design constraints.
• to motivate: identify painkillers rather than vitamins
• problem with current restaurant reviews: too much trouble to go back to computer after dinner to write review.
• feedback on the story boards from people outside of the project team, people in public
• visualize our progress, in terms of persuing new ideas, brainstorming, prototyping, getting reviews from people, finetuning ideas, etc.
• most people look at comments but don’t susunde put up comments. could collect data such as access numbers, number of people who visit, visiting frequency.
• brainstormed storyboarding and future scenario with finland
• shared deviceless idea for Finland
• carry around key ring sort of small device. there is intelligence in all objects. the device acts as a input output device.
• another scenario: window shopping. teemu is in a shopping center, and see something interesting. using the key ring. want to contact friend regarding the item. sort of a virtual wall(?). another version of shopping together (Danielle) idea.
• time line with milestones until the end of the quarter
• publish the ME310 method and experience with nokia. sharing design development experience.
• internship program
• contact nokia before we do user studies. nokia has experts in user study.
• can’t just collects a bunch of users. need to address ethical point of view and stuff.
• talk about our concepts and ideas with the nokia design team later.
• how are technologies used in each part of the scenario storyboards.
• why do each of the storyboards make it human.
• what does it mean for something to be human. (maybe start a topic about it on a emailing list).

[edit] Jan 18, 2007

Working on Dark Horse People: BDER

• Eric bought Brookstone slideshow keychain
• We attached a strap to it to make it watch-like
• Created comments on photoshop that will be displayed on device
• Post-its can be used for input

[edit] Jan 17, 2007

Brainstorming Darkhorse Prototype Ideas People: BDER

Choices of Ideas to Test

• Bubble: Users can generate information on their portable devices and all information will be tagged accordingly. Users will be able to view relevant information based on the tags.
• Spontaneous communication between global partners
• Deviceless by having chips in objects

• Decided to test Bubble idea
  • The device will be in the form of a watch
  • User will be able to spontaneously write comments on the device and the comments will be automatically tagged and uploaed. The user will write on the watch to input data.
  • The user can view information on the watch.

[edit] Jan 16, 2007

1. Global Meeting
2. Meeting with Teaching Team

Global Meeting
People: BDER, Teemu, Laura, Lasse, Mark

• Shared storyboards
  • Current/Future Friend/Date locator
  • Intelligent Device that uses GPS Info
  • Automatically uploading and organizing user generated data
  • Deviceless scenario by having objects around user have intelligence
• Bubble Idea: Tag everything including user profiles/accounts, event info, location info, photos, devices, user generated comments, news. This way nodes with common tags will be in the same bubble and will have access to each other. For example users that share a tag with a party information, a photo, and a light switch in a particular room will have access to all these things. This is a good way to manage and organize informaiton. It will also help in deciding what information is most relevant to a user in a specific situation.
• Task: to develop these ideas and come up with possible dark horse prototypes

Meeting with Teaching Team
People: BDER, Mark, Vic, David, Alissa, Micah

Summary of Feedback

• Afer presented the ideas that we came up with earlier that day
  • Nice Ideas
  • Afraid that the project is becoming to much software oriented
  • Try to think more about hardware solutions
  • Once we have a better idea about the hardware that we will be using the teaching team can help us a lot

[edit] Jan 11, 2007

Meeting with Stanford Teaching Team

From Mark Cutkosky's Notes

• Peer review -- we ask you to look at team Panawalk. Can get

hardcopy from them or use the PDF version that is posted on server. Comments from Mark, Larry, etc. are also available if you want to look but probably best just to go by the "template" of questions in the assignment description. Due next week.

• Your document & comments thereon are also available.
• Meeting time -- unfortunately we have a few teams that want to meet

after 5pm and not enough slots to accommodate them. We're looking for as much flexibility as possible -- like if one person can't attend in person but can dial in on the speakerphone that is OK.

• Nokia liaisons hopes you'll do a "Focus day" for detailed scenarios.

Encourage you to contact Bill Cockayne to plan it. Outcome of day shoud be: Detailed scenarios. Delphi group style.

• Suggestions:
  • Invite somebody from Cliff Nass or Byron Reeves group. Everything is

media. Graduate students from group often better than faculty.

• • New book is good layman's view of their research:
    • The Media Equation: How People Treat Computers, Television, and New

Media Like Real People and Places (CSLI Lecture Notes) (Paperback) by Byron Reeves, Clifford Nass .

• Contact Bill Cockayne. He has said he'd be happy to help: (bill@cockayne.com)
• Think about where Apple Inc. is known today... "digital lifestyle +

computers" (iPod, iTunes, Macs, iLife, etc.) and where they want to go with the iPhone.... In some sense Nokia is already there in the phone space and wants to move into a similarly broad area that Apple already occupies (although different than the particular one than Apple is in).

• We should also get you in touch with Gretchen Anderson from Lunar

Design on interface design -- she doesnt write code but she "storyboards" exactly what should happen & when so that the coders can do it.

• Vic: Storyboarding is great because forces you to get off the top

level. What it could look like & if a person does X then Y should happen.

• Dark Horse thoughts -- Trying to think about how constraining the

design space really is.

• And getting more "real" than the fall quarter stuff. What do you want

to do?

• Larry asks about global collaboration -- And recommends that get the

Helsinki team to do some storyboarding on their own too.

• Vic - and there are hardware opportunities too that might come up in

the context of your storyboarded thing. Like for example, you could think about video which is not just passively observing but influences people in some way. Persuasive technology?

• Larry -- time for the TTeam to stop "designing" things :-). You have

ideas too. Storyboard a good start. Stack of 3x5 cards, a videogame express yourself in as much detail as possible. "Who knows, maybe I may want a case that I can put my widgiewodgie in and make it defeat all attempts at communication & interaction."

[edit] Dec 6, 2006

Meetings with Students in NRC Palo Alto
IMPORTANT POINTS
- Research each item on abstract
- Look beyond 5 senses
- Our ideas our good, but look beyond that, brainstorm more
- Make sure that Stanford and Finnish team are coordinated

SUMMARY
- Meet Joe McCarthy and introduced ourselves
- Showed our presentation
- Tested screen sizes: what function were we testing? Helped us come up with more questions to answer. For example very portable devices that have all the functionality may not be popular because of usability issues.
- CFP2: Testing models of devices with people to find out what they want to communicate. It is very important to set up the experiment well to get out the right information. We could have provided them with devices that had functions that related more to the people's situations.
- Testing real size: position of the image of the person also affects communication. Virtual reality so that people feel closer: how do we deal with communication between sitting and walking person?
- Communicating the environment: there are cell phones services that send background noises.
- Emotion communication technology: shake object and transmit shake. feather that responds to input from remote location. Very useful to approach a common goal from different perspectives but want to avoid Stanford and Finnish team branching off too much in different directions.
- User case study
- Focus research on emerging technology. This way we will find interesctions between our ideas and available technology. We'll be able to build our ideas off of the opportunities of technology.
- Reseach each item on the abstract.
- Each technology
- what does human mean? etc
- Innovation day: Input from other people. Very very important to organize it well. Nokia can help with some things if we want to do it.
- Ask ourselves "Why isn't this idea that we have currently implemented?"
- Blogging is a possiblity

[edit] Dec 1, 2006

The benchmarking presentation as well as files that we have for the CFP we are conducting is uploaded onto the Stanford server.

The following are the instructions we were given for accessing the server,

Windows

  1. Open Windows Explorer (Windows Button + E)
  2. Click Tools > Map Network Drive 
  3. Click on Sign up for online storage or connect to a network server, click Next
  4. Select Choose another network location and click next.
  5. Enter [1] , click Next
  6. Enter the standard ME 310 login you use elsewhere.
  7. Enter a name such as: "ME 310 Documents Archive 06-07"
  8. Click Next and Finish 

Now you can access the ME310 file server by going to Network Neighborhood and clicking on the link you've created. Apple

In Finder click on Go in the menu bar at the top of your screen Choose Connect to Server. In the new window enter the address: http://wikibox.stanford.edu:8310/FileShare0607 Now click the + to add this to your list of favorite servers and Connect. Yes - for a large file the document server is better.

You can send them the instructions to access it. They can use the corporate login (login = "corporate", pwd = "liaison310"). I just tested that this works to give them access to the Document server CorpProjects folder.

[edit] Nov 15, 2006

Today the Stanford student team, along with their coach Robert Emery Smith and a team from Finland visited our lab. They presented initial thoughts about communication starting with a cool video shot at University Ave, Palo Alto showing how different people communicate remotely and in person. They then showed an exercise of how they plotted the communication landscape with "Human" along the Y axis and "Technology" along the X axis. Communication forms that appeared more human (e.g. hugs, shaking hands, smell) were in closer proximity to the Y axis, while communication forms that appeared more as technology (e.g. ipods, email) were in closer proximity to the X axis. In addition, the group looked at various gadgets, display technologies (e.g. 3D, holographic, projector based), visual technologies (e.g. feature tracking) and haptic devices (e.g. wearable glove, remote hugs).

We talked about the need for different types of communication (e.g. face-to-face vs. sms) and looked at various examples (both popular and failure cases) such as Yahoo Messenger's emoticons, Microsoft Word's paper clip, iPod, video conferencing and felt that it is better to find a pain-killer for communication needs rather than mere vitamins. In other words, tying usage scenarios to various communication needs might better help define what new designs and technologies we could bring to the table. The next steps involve interacting with common people whether on the street, family, friends, ourselves and discussing what are the current issues with various forms of communication, and creating usage scenarios of such experiences.