EXPERIMENTATION LOG — userNames, invitation build

 Aim

To get a text/username input working, and feeding into the fake code. 
Build animation/interactivity into the setup — grid, stage. 
Fix the sound issues. 

Precedents / context

Wk 6 studio feedback on usernames, and how I might build it into the experience. 

Process / methods

• The priority was the sound. I was watching videos and making sure I had the code right, but it got to a point where sometimes it worked and sometimes it really wouldn't. Thought I would just upload to github and test it. Doesn't work very well in chrome, works perfect in firefox. 

• Researched the different options for text input — keyPressed(), createInput(), etc. KeyPressed() didn't seem to be able to store information that easily, and I didn't know how I might tell users to engage in that way. CreateInput() makes one of those standard web text boxes, so there's an immediate familiarity with what you're being asked to do. 

• Finally started coding the setting up of the physical theatre, still with a lot more to do. Ran the code out of the screen, and faded in the grid. 

Reflection on action

• The sound/browser issues were frustrating, especially given the agony spent over it, but it's good to know that my code was fine most of the time. It's weird with firefox though— the fullscreen doesn't full screen, so you have to scroll to get to the bottom. The colours are like SUPER rgb, which is quite a shock honestly. 

• Regarding how I would go about setting the username, I think leaving it completely up to the user was the easiest, most streamlined and organic option. Random generating from a set of words I determined seemed rather unnecessary and awkward within the setup/invitation space? Felt like it could be rather drawn out, or otherwise miss a step or two from the user's point of view. 

• The username/text input came with a bit of a learning curve and I wasn't sure if I would be able to execute it, but it seems to work. Was happy that I could get it to write in the fake code e.g. (username input).body(engage);, and start working it in to other parts of the experience. Still unsure if I can retrieve it from another file/sketch once it's all online? 
  
  Still questions around how the user progresses through the screens — the username screen is progressed by the 'enter' key, as part of the input, but that's not foolproof. And is it then weird to switch back to clicking the mouse?

• Also last week I had planned to record the speech for the fake code but now I'm not too sure – will it make the whole setup too long? Does it make it tedious to have to go through all the audio clips to get to the later interactions? 

• I like the big 'Cyborg Witch Theatre' at the start. Was thinking about Nicky's comments on type and scale, so I think it's a much needed visual element that's also a good conceptual cue for what the site is. I don't know if the placement could be better? Especially with where the comments start to hang from. 

Reflection for action

• Get help from Will around browsers and linking pages together on Github, and accesing the text input from another page. Also user testing with some other people, and doing some research/troubleshooting into what the specific problems are. 
• Look into another sound element (background/white noise/reverb) instead of speaking the fake code. 
• Streamline the setting of the stage — work out how to move the text box out !!! And when to stop one sketch and start another.