Back to Projects

Human Computer Interaction

April 2026 semester

EmotiTrack

A mobile and smartwatch concept that helps students notice stress and calm down, designed from a user survey through requirements and architecture to an interactive high-fidelity prototype.

  • Team of 5

Project Files 2

What I learned

The challenge

Designing for students in distress meant earning their trust: our survey showed people worried most about how accurate and reliable AI detection would be, so consent, privacy and offline support shaped the design.

The experience

I led a team of five through both assessments, coordinating our work from the user survey to an interactive prototype and a development plan.

Skills I developed

  • User research
  • Requirements analysis
  • Usability heuristics
  • Prototyping (Figma)
  • Software architecture
  • Team leadership

01The problem

Stress, emotional overload and difficulty self-regulating affect many university students, and support is not always at hand when it is needed.

The project took on UN Sustainable Development Goal 3 (Good Health and Well-Being), focusing on emotional wellbeing.

02What the team built

  • A mobile app paired with a smartwatch that analyses authorised biometric and behavioural indicators
  • Grounding and breathing exercises that also work offline, wellbeing reminders, and a history of insights
  • Consent-based SOS support for emergencies
  • Low-fidelity and interactive high-fidelity prototypes covering onboarding, monitoring, interventions, SOS, history, settings and the smartwatch

03Software engineering process

  1. Research

    A user research survey shaped the features. For example, respondents rated offline access as highly important, which led to offline grounding and breathing exercises.

  2. Requirements

    Functional, non-functional and data requirements, written up with Volere requirement shells.

  3. Design

    A technical architecture, a technology stack, data and privacy rules, and prototypes checked against Nielsen’s 10 usability heuristics.

  4. Planning

    A software development methodology for building the system, with sprint planning and a Gantt chart.

04How we worked

Each member owned specific sections, but decisions that affected several parts (features, technology, navigation flow) were discussed together, and members checked each other’s work. The team worked through WhatsApp, Google Meet and shared online documents.