NUDGE-HCI Project
Exploring human-computer interaction and affective computing to build interfaces that respond to user behavior.
HCI Researcher & Developer mapping the space between human emotion and digital architecture.
I start by watching where people hesitate, get confused, or leave. Fixing confusion early saves weeks of rebuilding interfaces later.
I write the frontend code and the backend APIs myself. That means the screens work properly with real database data, not just static mockups.
Every button click, status update, and loading state should tell the user what just happened. If an interface leaves someone guessing, it failed.
Exploring human-computer interaction and affective computing to build interfaces that respond to user behavior.
Mapped out patient records and admin workflows to reduce cognitive load in high-stress hospital environments. Directed the product vision.
Built a full-stack prescription manager focused on reliability for daily health routines (Python, Django).
Designed user flows and profiles for a digital learning community, focusing on safe, structured communication.
Built web applications, improved search rankings, and wrote technical guides for users.
Developed frontend pages with clean, responsive code and improved load speeds. I also wrote straightforward documentation so users could get things done without getting stuck.
Studied computational emotion recognition and how computers detect human emotional signals.
Learned how algorithms analyze facial cues and physiological data to estimate stress. It gave me a practical foundation for designing interfaces that don't overwhelm people.
Practiced active listening to support people through stressful moments and keep communication safe and clear.
Had 1-on-1 text conversations with people looking for support. It taught me firsthand how much wording, tone, and pacing matter when people are overwhelmed.
Studied data structures, algorithms, databases, and computer systems.
Gained the technical foundation to write production backend code and communicate directly with engineering teams without misinterpretations.
Languages I use for backend logic and user interfaces.
Tools I rely on for databases, APIs, and servers.
Empirical methodologies and user modeling for affective, human-centered systems.
Communication, problem-solving, and cross-functional leadership.