Tutorial TouchStudio April 16, 2011Posted by reto wettach in innovation process, mobile, prototyping tools.
They gave a nice introduction, starting with the Commodore 64 and how the main experience was to have to program this device. Exactly this experience made the C64 so successful. However, in today’s mobile phone, there is no programming environment, despite the fact, that all over the world for many people the mobile phone is the only access to computer technology.
Then they pointed out, how today’s IDEs are really supportive and have a lot of intelligent features which support the programmer while typing. However, text input on smartphones is not really suitable for programming. So, they invented TouchStudio, a programming environment for the mobile phone, where on can program with “one finger only”.
I really like the idea behind TouchStudio – and the first demo was quite impressive. It took the programmer less than a minute to program an app, which would turn off your music player when you turn the phone with the display facedown.
When working with the TouchStudio I was quite impressed with a couple of text editing features they build: the zooming to a specific line of code works extremely intuitive, the selection and completion of commands is also well executed.
(Here is a video about TouchStudio)
They already implemented some interesting access to the phone’s internal technology as the camera or music player.
The performance is also good: I programmed some Processing-like animations and they worked fine.
The code itself is still displayed as text. I am wondering whether it would add to the joy and clarity if the code would be displayed a little more visually, similar to scratch.
In some cases one needs to provide the software with too much details, e.g. a given color in the draw commands would be sufficient.
Currently scrips cannot be shared with friends or sold in the marketplace, which is another downside, but they are working on this.
And not all sensors of the phone are accessible, yet, but I guess that this will also soon be changed.
One thing I could not find out was how to change parts of the code, which are in the middle of the code, e.g. I wanted to change a “while”-statement to a “for”-statement and could not find a way to do this.
I love this tool and I am looking forward to the innovations which will happen, once lots of people can play with it!
Tools for Innovation – Part I November 17, 2006Posted by reto wettach in innovation process.
1 comment so far
Through a couple of projects we have been doing at the Interaction Design Lab, I am asking myself, how to develop “Tools for Innovation”. By this, I mean software supported tools, which inspire and help to find opportunities and interesting interrelations.
The first tool, which I am looking at, is “Mapping”: Through a multi-dimensional arrangement of new ideas and/or existing projects one might be able to spot areas of opportunities. My professor, Hans (Nick) Roericht, and his team wrote about Mapping:
gesucht ist eine art der darstellung, die aufgrund ihrer inneren struktur, geschaffen durch “polungen” analog den himmelsrichtungen, die orientierung innerhalb eines sujets erleichtert.
(we are searching for a diagram, which supports the orientation within a subject, based on the diagram’s internal structure, which is constructed through “polarities” – similar to the directions on the compass)
Mapping should be used – according the Roericht – for the following purposes:
…für die systematische variantenbildung.
…zur gliederung von begrifflichkeiten.
…zur strukturierung der eigenen gedankengänge.
(…for systematically producing variations.
…for the classification of the terminology.
…for structuring thoughts.)
Together with Fabian Hemmert, Andre Knörig and Julia Werner we developed a flash prototype of “Mapping”-tool, so far a two-dimensional solution
For a project about tactile mobile interaction, we used 11 axis, which could be selected within a pull-down-menue:
Based on the selection of axis the projects would be rearranged dynamically. Here a detail view:
(I did not upload the tool yet, because it is still kind of buggy)
I am wondering, how to further develop this tool. Some ideas we are having are related to more dimensions, but mostly easy access of the project library and the various evaluations. Furthermore it would be interesting to apply Web2.0 ideas to this tool. Any comment welcome!
Talk on Prototyping by Yaniv Steiner November 17, 2006Posted by reto wettach in innovation process, prototyping tools.
1 comment so far
He is also talking about the process, in which prototyping should be embedded:
I especially like Yaniv’s thought “keep it open”: prototyping should always stay a step within a process, never arrive at the goal!
(Regine from wemakemoneynotart went to Yaniv’s talk and wrote a nice blog entry)