Currently having a nose around the a-frame design tool as a way of designing some scenes. I have a vague idea of what I want to see and hear but I am looking at what existing tools offer.
Does reading the documentation become a way of testing the tool and becoming a way of thinking about its design and limitations? By taking some ideas and mapping them to the desired or potential use cases, we can begin to look at the affordances and limitations in the documentation and the existing interface.
When this is contextualised, then might it offer ways of thinking about the tool’s wider context: in this case, designing for Augmented and Virtual Reality? How might these be repurposed as a method, if one takes that route? I hope to develop this in the new year and to think about how it can be applied to data driven work.
No Comments