Chris Greenhalgh, 2017-02-16
These specific projects are all suitable for HCI or CS
The muzicodes system (http://dl.acm.org/citation.cfm?id=2986444) allows musical phrases to be used as triggers in an interactive system. For example, when a musician plays the first few notes of a tune this might be defined as a code that starts the accompaniment. There are several possible projects that would use and build upon this system (and others would also be welcome).
Design, prototype and evaluate a social online version of the muzicodes system. For example, this could be a competitive platform where one user can set musical challenges for other users. Or it could be a collaborative/user-generated content platform, where users share compositions incorporating muzicodes.
Design, if necessary extend and then evaluate an application of muzicodes to live group (rather than individual) performance. You would need to identify and recruit the group of musicians to work with. You would then need to work with them to explore and work up one or more specifically collaborative ways of using muzicodes within a performance setting. Given the dynamic nature of muzicodes the performance would need to have a significant element of performer choice, e.g. semi-improvised elements.
Databox is a platform that allows individuals and households to manage their personal data and allow other parties to run apps or computations against their data without giving their data away (http://www.databoxproject.uk/ https://youtu.be/NBxMk4LMGbk?list=PL9UQcjjmGF3cUoLmvvfrepPAM62sxx5_3 http://www.eecs.qmul.ac.uk/~hamed/papers/CAN2016Databox.pdf http://www.eecs.qmul.ac.uk/~hamed/papers/Human-Data-Interaction.pdf). The first public developer release of Databox will be in March 2017. The kinds of data that it might have would include: home Internet of Things data; personal activity data, e.g. location, exercise; home electricity usage; home device use, e.g. media viewing. There are several possible projects that could be done based on Databox (and others would also be welcome).
Identify a potential application area for Databox, recruit relevant stakeholders, and work with them to design, prototype and evaluate relevant Databox application(s). Prototypes may be of varying levels of fidelity (paper mock-ups through to complete functional Databox applications).
Databox is intended to act (amongst other things) as a security and control point for Internet of Things devices in the home. Research, design, prototype and evaluate specific examples of IoT device use with Databox. For example, this may include introducing the device into the home, associating it with the Databox, configuring it, using and controlling it through Databox applications.
Databox will implement a range of security policies and employ a range of security mechanisms, for example for authenticating users, managing accounts and devices, managing access to data. Security almost always involves complex trade-offs, for example with ease of use and compliance. Research and evaluate the initial approaches to security proposed for Databox; propose and evaluate refinements or alternatives of these approaches.
The first release of Databox will be single user; initial designs have been made for multi-user household use. Starting from these initial designs, recruit and work with households to evaluate and refine approaches to using a single Databox with multiple users. This includes issues such as sensitivities around highly individual data sources (e.g. one person's location or social media) on the one hand and shared/collective data sources (e.g. activity detected in a room, appliance and shared device use, shared cameras).
Databox is intended to support an open ecosystem of apps that use personal data. To support this ecosystem it is intended that self-selecting Databox users/developers will choose to scrutinise the actual behaviour of Databox apps in use, and their reports (e.g. rating) will allow other users to make informed choices about which apps to use. Design, prototype and evaluate one or more approaches (e.g. UIs, tool sets) for such auditing of Databox apps.
Geotracks (http://dl.acm.org/citation.cfm?id=2967181) is an approach to adaptive music that tailors the listening experience for a specific journey. Initial experiments used an Android player, DaoPlayer (https://github.com/cgreenhalgh/daoplayer). In parallel, a "semantic player" application has also been developed (https://smartech.gatech.edu/handle/1853/54596).
The initial geotracks were manually authored, largely by editing JSON configuration files. Design, prototype and evaluate a web-based system for non-experts to author geotracks and geolists (effectively location-based playlists). Variants of this project could emphasise adaptation of the playlist as a whole or adaptation of a single track.
One key application envisaged for geotracks is the journey to/from a particular event, such as a concert, gig, film or club. Design, prototype and evaluate an experience using geotracks for the pre/post- event journey. You would need to identify a specific event, ideally recruiting key stakeholders in the event to contribute to the design and evaluation process. You might also need to address authoring challenges to create and deliver the specific experience.
In general am interested in:
Most of my current work is in mobile and ubiquitous computing (including mobile games and cultural experiences), and I have done a lot of work developing mobile applications on Android as well as web applications and collaborative systems.
Most of my projects combine (to varying extents) software development, interaction design and user studies.
I'm happy for you to propose your own projects, ideally related the above themes.