CRITIQUE SUMMARY — WK 8 Studio Session

GENERAL FEEDBACK:

• Think about what you're presenting in Wk10 — is it a final design outcome? Is it a set of experiments? Put boundaries and definitions around it so they know how to contextualise the project and what to give feedback to.
• Be strategic in what you put your time to in these next two weeks. 

CRITIQUE:

Andrew:

• Window resizing/clipping plane — it's being weird(? not transparent so shouldn't be an issue) Look further into the windowResizing function in javascript. Send over code. 
  
  Same with the create input text box, hard to know what's going on without seeing the code. Might have to hide it? 
  
  
• Don't prioritise the troubleshooting — get the interaction and experience working as best as you can first. Can specify that the optimal size is the dimensions of my comp, etc. 
• Visual style is working well. Bringing in the type has helped. 
• Should test the readability/accessibility of the colours — run through a colourblindness app. 
• Linking to another page — window.load, window.open, triggered by an object / time / event
• Retrieving the username — pass variables between windows of the browser. Can do by accessing/calling local storage? 
• Illustrations for poetry page. Are they going to be glitchy and pixelated like the cloud image or referencing more traditional print? Tying the poems into the imagery/type really starts to gives the whole thing/setup/stage more purpose, contextual relevance. 
• The floating screens working well to construct the stage, same with the speech and sound effect — visceral but virtual. Speed — could slow loop of draw to make it smoother for slower computers. But a lot of it is dependent on external factors like (what else is running in the browser, computer specs, etc.)

Adrian:

• Visual style working well, the "clues" are working to give you information about the experience / what you're supposed to do within it. Working as it's own kind of worldbuilding. 
• It might work better to have the transition into the first stage as an automatic load, and stage 1 to 2 as a manual button/click. 
• Hands interaction — Think super simple. Might work better to make the variables controlled by the hands additive, so the movement/progress is not determined by how jumpy as it actually is. That it can't go backwards. 

CRITIQUE OF CRITIQUE

• Hands interaction — think Adrian's suggestion of controlling the interaction/movement in one direction is really helpful, helps me direct the potential concept and interaction in a workable way. 
• Will definitely test the colours for accessibility — need to go back and reevaluate them regardless. 
• Illustrations for poetry page — I think this would be really cool. The potential to bring in glitches and more of a digital materiality is also really cool. Gifs I will definitely look into if I have time. 

ACTION LIST 

• Priority items — Getting the hands stage to the same place. Giving it narrative significance (!!!!) and purpose. Coding this. Making the image screens for it. 
  Linking the experience together. 
  Working the whole experience together — sound, more atmosphere, getting the voices right, type elements. 
  Illustrations for the poems. 
• The hands stage is definitely the priority at this point. Go back to thumbnailing and concept drawing to work it out. 
• Other priority till Friday is to link the webpages together so that you can bring any problems to Will. And comment your code properly, zip up and send to Andrew. 
• Do I need an endpage? 
• Start thinking about the presentation and how you might construct and tell the story of the project(?).