In our last post, we introduced an alternative syntax for describing mobile processes. Now, we are facing the challenge of getting feedback from users. We are contemplating two directions. The first one is to create a Amazon Mechanical Turk Task and ask Turkers what they think about the syntax. We have done this in the past with the basic Tweetflow syntax and we got results really quick. The second one is to built an actual editor and include it in our app qlauncher. The second alternative is to implement an editor (which is a lot of work) and to test it directly in the app. This approach has the main challenge how to include test cases and how to motivate people to use the syntax. We are looking into games where users can “play” with the syntax. This needs obviously a game to play with and we haven’t found the right game to play . Maybe, people could CREATE a simple game with this syntax.
We have tinkered with the syntax and modified it a bit to distinguish context from the rest:
This gives us the possibility to attach different context for different parts of the process and to modify each process according the context:
Our idea is based on previous work where we introduced the concept of context channels. We plan to extend this work towards social tuple spaces that work well with Tweetflows and hopefully will us help to come up with the final design for the mobile process language description.
your ikangai science team