I feel that I have a better understanding of the process now when we are working in module 3. I have learned from the two previous modules that the first week goes by so quickly and that it is important to get started. In this module, we have struggled with knowing what we should focus on during the start. Can we really start coding when we don’t know what kind of kinaesthetic experience we want? And what counts as a kinaesthetic experience? We hade the discussion if it just the feeling and awareness of our body motions or dose feelings like when you can feel in your body something approaches also a kinaesthetic feeling that we can work with even though it doesn’t is the movement of the body in itself that are making the move.
Therefore it was nice to get some coaching and help with clarifying what we are doing. We got the advice to explore both the movement and the code at the same time now in the beginning and to start simple. To create a simple sketch and then take a step back to see what movement we have and how we can use it to interact. Another good reminder was that we should focus on designing for the movement of the body and not for the screen. From Roel we got the advice to move away from the camera feed. I think that can be helpful, and perhaps that helps us not get too attached to how the movement is looking in the screen representation and let us explore bodily movements more freely.
We understood kinaesthetics as how you perceive your own body both the mechanical functions of the body and the feeling that a movement creates. Also, if a movement in a, let’s say, narrow area creates a bodily feeling, it could be counted as a kinaesthetic experience even though it is the surrounding that affects the bodily experience.