HCI Projects

Project #1: Conduct an Human-Computer Interaction experiment

Timeline

25 sept. 2025:
- Pair up with a partner in the course and notify the teacher on the project's pad
- Start to design your experiment during the course
2 oct. 2025: Present your first data/results
9 oct. 2025: Formal presentation of your experiment: Experimental design, Procedure and Results

Guidelines

The objective of Project #1 is to learn how to design and run an experiment. You will implement this by answering the question: How do <two devices>' efficiency compare to acquire targets?

Steps:

Design your experiment
Run your experiment. Use a ready-made platform, e.g.:
Analyse the collected data
Present your work (Oct. 9)

Your report should:

Present your task and justify all its parameters that you controlled (1D vs 2D, target width and distance, etc.)
Present your conditions (precise apparatus, etc.)
Present and justify your experimental design (Independent variables (= conditions), dependent variables (= measures), number of repetitions, training, justification to stop recruiting participants, etc.)
Present and justify the choice of your participants (age min, age max, mean age, gender as reported by them, occupation, habits with devices relevant to your experiment, etc.)
Present the collected data
Conclude on your experiment
List what you learned, what surprised you, and what you would do differently if you had to redo it again

Project #2: Identify a research question (RQ), propose and test a solution

Timeline

16 oct. 2025: Pair up with *another* partner (different from project #1) and notify the teacher on the project's pad
Before 23 oct. 2025: Have your proposed RQ validated by the teacher
13 nov. 2025: Present your first draft of literature review, prototype, and experimental plan
20 nov. 2025: Fine-tune your literature review, prototype, and experimental plan
4 dec. 2025: Mid-project presentation. Then start running your experiment
11 dec. 2025: Present your first draft of analysis
18 dec. 2025: Present your analysis of the results
8 jan. 2026 midnight* at the latest: Send the report to the teacher
15 jan. 2026: Final defence

* If you submit the report after this time, we will not be able to guarantee that we have read it by the time of your presentation. Given the limited time for presentations and questions, you risk that your time will be taken up by clarifying ambiguities that the report could have addressed. You will not receive a grade for this course until you have submitted your written report.

Guidelines

The objective of the project #2 is to identify an HCI problem, propose an original solution, and evaluate it. You must work on an interaction for which you can anticipate benefits that you state clearly.

1. Choosing a problem

Each pair of students chooses the HCI problem they want to address in their project. The research question is “moderated” by the professors. The idea must be relevant to the course: the solution must be original, your motivations must be clearly stated and convincing, and you should be able to evaluate the interaction with a prototype (which can be anywhere between high and very low fidelity).

The project must be validated by the teacher and presented in class during the first project session.

2. Design

2.1 State of the art

Once a teacher has validated your project's problem, you must make a quick review of the state of the Art: what approaches have been tried for your problem? Which systems were implemented? What worked and what didn't?

2.2 Propose a solution

Building on the state of the art, you must design an original solution for the identified problem. The design must follow a user centred approach: the interaction must be designed so that is satisfies the users’ needs as well as possible. You must be able to clearly state why this solution is suitable for the problem and could reasonably be expected to improve the users' experience.

3. Evaluation

You must evaluate your solution through a user study.

3.1 Prototyping

You prototype the interaction to evaluate it. Depending on the feasibility, you create either a low or a high fidelity prototype. You will be able to prototype the interaction with specialised input/output devices from Fabrication Laboratory (FabLab) on the campus (called FabMSTIC) and E310 at ENSIMAG (documentation). You will be able to use rapid fabrication tools to build your own devices. Do not hesitate to ask your teachers for more devices if you are looking for something that is not available there.

3.2 User Study

You test the proposed solution by having non-members of the project use it. You evaluate the strengths and weaknesses of your proposed solution through examining interaction with your prototype. Take care to separate technical problems (the prototype does not satisfies the specifications) from conceptual problems (stemming from the analysis and/or the design). You can evaluate the solution through objective (e.g. is the solution faster than the status quo) and subjective (e.g. do users prefer this solution) measures. Note that a negative result (i.e. the solution does not improve the user experience) is a valid finding. In this case, discuss possible reasons.

Deliverables

Report

The report (5 pages maximum) should include the following content

Presentation of the scientific question addressed by your study,
rapid overview of the related work,
presentation of your solution,
presentation of your results,
a general discussion and conclusion about your project.

Presentation

Presentation (same outline as the report) + Questions (20 minutes total)

Please select your presentation slot here. Include your group number when booking the presentation time. Please coordinate with your partners and only book one presentation slot per group. Make sure to arrive ahead of your scheduled presentation start with your presentation materials ready - the projector has an HDMI connection, should you require anything else please make sure to let us know well in advance. As your presentations are back-to-back please do NOT enter the room unless the door is open (and the previous group is finished).

Example projects

Example projects from 2024-2025

Further examples can be found from previous years' Human in the Loop and AR VR courses Schedule/Class notes