Monday, 1 March 2010

Reading Circle 6: Chapter 7

Attendances: Josefin, Nathnalie, Christofer, Åke, Yathika, Fanny, Peter, Jacob, Cenlan

Information Appliances
: Having one appliances for each task. We think that it would be better to have one machine that does most. And maybe separate the most standard tasks in their own appliances. It have downsides that you have to learn a lot of difference interfaces even if they will be easier to use. But splitting up the appliances is troublesome due to the "barriers".

Convergence: Mobile phone is a good example of convergence. We as a group prefer convergence.

Invisibile UI: Chapter is a lot about Ubiquitous Computing. We think that Invisible UI is already out there in some way, for example accelerometer in the iPhone could be explained as a Invisible UI. But you still have to learn the UI, which we thinks is a good think opposite to Dourish that wants everything to be so natural that you don't have to learn at all.
Something becomes invisible because we learn it. A better name/solution would be a Natural UI meaning that it would feel natural to learn it.

Social & Technical: -

Physical & Symbolic: There is no point of using a physical interface if its not symbolic. You have to symbolize otherwise it makes no point at all.


Questions to answer during the reading circle:

What are the main points of the chapter.
Obviously a conclusion about the book. Where he often explains it better and easier than in the main chapters.

Unclear parts in the book.
What the difference between Representational view and Symbolic view?

Find useful info that can be used in our projects.
Being a conclusion there is not a whole lot new stuff that we haven't already mentioned

Come up with ideas for a possible workshop.
Being a conclusion there is not a whole lot new stuff that we haven't already mentioned

http://www.csdl.tamu.edu/~zacchia/research/Readings/books/ActionIs.htm

Monday, 22 February 2010

Reading Circle 5, Chapter 6: Moving Towards Design

Today´s agenda:
* A common framework
* Design Principles (six principles)

Dourish writes that It would be inapropriate to give guides and principles here, but he does anyway:
1 Computation is a medium
Yes, but we don't really agree with the example with learning to program since, that's using computers really.

2 Meaning arise on multiple levels

One artifact can have different meanings to different persons and different situations.

3 Users, not designers, create and communicate meaning
Yes, users understand meaning individually

4 Users, not designers, manage coupling

Maybe, but the designers should make a strong coupling that help users understand. On the other hand the designer should try to make an open system so that the user can customize the usage.
Maybe the designer should use a lot of user testing to see how users prefer to use the system and then develop that usage further. Kind of like in architecture when you don't build pathways until you see where people are walking.

5 Embodied technologies participate in the world they represent
Not clear what he really means

6 Embodied interactions turns action into meaning
Make logical systems, that map action to meaning.



Questions to answer during the reading circle:


What are the main points of the chapter.
What you think is obviuos is not necessarily obvious to someone else.


Unclear parts in the book.

principle 5 above.


Find useful info that can be used in our projects.

The ideas are a good backdrop for thinking when designing, even though they aren't a method.


Have an interesting discussion.
We think most of this is pretty obvious but maybe it's good to get it in writing.

Come up with ideas for a possible workshop.
20 design and then let other users use it and see if they understood it in the same way.
Foldable "design" each person designs a small part and then see the full design.
Guide another person through a maze (he shouldn't see it) see how the communication works.



Until next week: Read chapter 7!

Attendants: Magnus, Peter, Nathalie, Josefin, Christofer, Jacob, Yathika, Fanny
Secretary: Åke

Monday, 15 February 2010

Reading Circle 4, Chapter 5: Foundations

Today´s agenda:

Three aspects of meaning - plays a role in understanding embodied interaction.
Ontology - understand the computational world, which through we operate.
Intersubjectivity - directness of our actions & the effects that our action are designed to cause
Intentionality - we share the world with other individuals.

Coupling - understand and interpret the interactive systems and operate through them.

Coupling in Metaphors

Embodiment

Questions to answer during the reading circle:
What are the main points of the different chapters.
The aspects of meaning in embodied interaction. the effects of what our actions cause. How we share the world with other individuals. We all have different views of what our world is.

Unclear parts in the book.
Intentionality - what a system is suppose to do.
Intersubjectivity- the communications between users, through a system. the importance of what a system really can do for a person.

Find useful info that can be used in our projects.
No not really, but we did get useful info about the metaphors and coupling.

Examples we can relate to which reflects the ideas.
We couldnt find anything new to reflect ubout. But we can reflect about the coupling and metaphor part we learned about in the course ubiquitous computing.

Have an interesting discussion.
We did have discussions about what the author really want to tell us. And about aspects of meaning.

Come up with ideas for a possible workshop.

Intentionality and Intersubjectivity. Make people design things and then see how other people percieve and understand it. Like Twitter. The way people use it was not the purpose the designers intended.

Until next week: Read chapter 6!

Attendants: Magnus, Peter, Nathalie, Josefin, Christofer, Jacob, Yathika, Fanny

Monday, 8 February 2010

Workshop

Preliminary date for workshop: 24/3 (Wednesday week 12)

Reading Circle 3 - Chapter 3 and 4

Todays agenda:
Ethnography, Ethnomethodology, Technomethodology, Anthropology
Accountability
Embodiment
Phenomenology: Husserl, Hermeneutic, Schut'z, Merleav-Ponty
Physical world, Lebenswelt
Space, place and locales
Sociology in HCI

We decided too only read 1 chapter until next week.

Attendants: Nathalie, Josefin, Jacob, Åke, Yathika, Fanny, Peter, Akbar, Cenlan
Secretary: Peter

Chapter 3:
What are the main points of the different chapters?

The main point of the third chapter is that humans don't work in the same way as computers. The outcome of that is that we can't divide the order humans do tasks in the same way as computers.

Unclear parts in the chapter?

There are many terms in these chapter that are hard to understand, which makes the chapter hard to read. And maybe we underestimated the time we needed for each chapter.

Find useful info that can be used in our projects?

The file example. [p, XX]
The planning model. [p, 72]

Examples we can relate to which reflects the ideas?

Social Computing is when you design computational systems with the social aspects of the user in mind.

Have an interesting discussion?

Our discussion is mostly about the terms we wrote in the Agenda.
Ethnomethodology: How people use their everyday experience to manage their activities.
Technomethodology: Designing technical systems with ethnomethodology in mind.
Accountability: Accountability is that you should be able to see what is happening. The computer system has to hold account of what is happening so users can see what is happening.
Space: Space is largely concerned with physical properties. It concerns how people and artifacts are configured in a setting. For example, how far apart they are.
Place: A place is a "space" where social understanding convey appropriate behavior framing for an environment.
Locales: Locales is about using the space for interaction.

Come up with ideas for a possible workshop?


Ethnography of an Air Traffic Control Center. [p, 64]



Chapter 4:
What are the main points of the different chapters?

Take what we experience (phenomology) and making it real by giving it a body and a meaning.

Unclear parts in the chapter?

This chapter was not as unclear since it more or less talked about how different people had developed the word Embodiment. One bad thing about the chapter is that it does not have any examples.


Find useful info that can be used in our projects?

We didn't not find anything particular useful since most of the chapter talked about how differnet persons had developed the term Embodiment.


Examples we can relate to which reflects the ideas?

We did not find any examples in this chapter. It is hard to apply it to a real system, more a way of thinking.


Have an interesting discussion?

Embodiment has played a different role for each of the phenomenological positions for all of the researchers that has been named in the chapter.

Embodied Interaction is the creation, manipulation , and sharing of meaning through engaged interaction with artifacts.

Come up with ideas for a possible workshop?

See chapter 3.

Monday, 1 February 2010

Main points of the chapters we have read for today.

Chapter 1 - A History of Interaction

Computers will change...
Phenomenology - "is primarily concerned with how we perceive, experience, and act in the world around us."

Chapter 2 - Getting in touch

Ubiquitous and tangible computer systems.

Discussion:

Is it true that the computers will disappear, become hidden?
People wouldn't want them to disappear today but eventually they will. Every day we see something new being produced that draw us closer to a more and more computerised living.

Where can we find computers, in the office is obvious but not so obvious where in your home. Computers can be embedded in basically anything today but what would the use be.
- We wouldn't want computers everywhere though. One problem is that it will affect our privacy.
In the future we will get even less privacy but it will probably be accepted. As we can see today most people accept less privacy being introduced.


For future RC’s we decided:

- If it is possible we would want to do a workshop instead of an oral presentation of the book.

-- Goals for each week --
What are the main points of the different chapters.
Unclear parts in the book.
Find useful info that can be used in our projects.
Examples we can relate to which reflects the ideas.
Have an interesting discussion.
Come up with ideas for a possible workshop.

Who was here: Nathalie, Peter, Yathika, Jacob, Fanny, Magnus, Åke, Cenlan, Baixi, Christofer.

Wednesday, 27 January 2010

First meeting

We are going to read two chapters each week and everyone is going to read the whole book. We are also going to meet according to the schedule and everyone was here today :)

Util next week we will read chapter 1 & 2 and discuss it on monday week 5!

Have fun!!