AI-assisted

Live

UI Design

HokieHustle

Challenging developer's bias and turning a campus-wide problem into a local web solution.

TIMELINE

2 weeks

ROLES

UI Designer, Developer

TEAM

3 developers, 3 designers

SKILLS

UX interviewing, AI-coding

Overview

The Platform

The VTHacks Hacker App is for participants, judges, mentors, and organizers to handle registration, coordination and live event updates in one place.

The Problem

See progress as the user completes the application. Instant system feedback, compared to throwing an error upon a submit try.

Solution

  • Instant user-system feedback and progress indicators.

  • Added a humanistic and warm feel through content design (verbiage) and overall user interface.

  • Smarter and more intuitive question form types.

"We [designers] “touch” code not by manually typing every line, but by engaging in a fluid dance - moving from the design canvas to code and back again, using live prototypes to inform and mold our thinking in real time."

Jacquez, Katie. "Code Is a Design Material." Google Design

Project

VTHacks

Timeline

2 weeks

Role

UI Designer + Dev

Category

App redesign

PROBLEM

The core problem surfaced early:

Patients managing care across multiple providers are overwhelmed with multiple portals, login credentials, and inconsistent data formats. In emergencies, this fragmentation can be life-threatening.

Patients managing care across multiple providers are overwhelmed with multiple portals, login credentials, and inconsistent data formats. In emergencies, this fragmentation can be life-threatening.

Patients managing care across multiple providers are overwhelmed with multiple portals, login credentials, and inconsistent data formats. In emergencies, this fragmentation can be life-threatening.

HEADER SECTION

s

Before

After

HERO

text

Before

After

INQUIRY

Affinity mapping

Raw interview data

88 work activity notes in
parent-child themes.

We also incorporated client-sourced data from a prior paper prototype study, which was what this project initially stemmed from.

Guiding the design

Guiding the design

Guiding the design

Fragmented record access

Fragmented record access

Fragmented record access

Patients had no mental model for which portal held which records, leading to forgotten credentials and missed information at critical moments.

Emergency information barriers

Emergency information barriers

Emergency information barriers

Responders needed critical details like allergies and current medications surfaced instantly, not buried behind a login.

Inconsistent portal language

Inconsistent portal language

Inconsistent portal language

Varying naming conventions across portals made navigation unpredictable, especially for vulnerable users.

Caregiver access complexity

Caregiver access complexity

Caregiver access complexity

Managing a dependent's care required role-appropriate access without compromising patient autonomy or privacy.

We built models to translate our research into design constraints

We built models to translate our research into design constraints

Persona strategy and setting the scene

SOLUTION

A Figma click-through prototype was built from low-fidelity sketches and a physical paper mockup. The prototype covered the app's core task flows.

Concrete data is important for healthcare

Concrete data is important for healthcare

Quantitative research methods we used

Benchmark tasks

Benchmark tasks

Benchmark tasks

Scaling incrementally in difficulty to measure task completion accuracy, execution speed (seconds), or error rates

after each benchmark task…

after each benchmark task…

after each benchmark task…

NASA TLX

NASA TLX

NASA TLX

Subjective assessment to measure the perceived mental, physical, and temporal workload a user experiences while performing a task.

paired with…

paired with…

paired with…

Think aloud data & usability questionnaire

Think aloud data & usability questionnaire

Think aloud data & usability questionnaire

When collecting our subjective data during the empirical evaluation, we found some positive design choices and some areas of improvement.

Unexpectedly…

Unexpectedly…

Unexpectedly…

Some buttons were too small

Some buttons were too small

Some buttons were too small

Complex tasks were completed faster than anticipated

Complex tasks were completed faster than anticipated

Complex tasks were completed faster than anticipated

Linking health portals lacked visual confirmation

Linking health portals lacked visual confirmation

Linking health portals lacked visual confirmation

Users and designers disagreed on which tasks were hardest, relative to other ‘easier’ tasks

Users and designers disagreed on which tasks were hardest, relative to other ‘easier’ tasks

Users and designers disagreed on which tasks were hardest, relative to other ‘easier’ tasks

But thankfully…

But thankfully…

But thankfully…

The dashboard layout helped users orient quickly

The dashboard layout helped users orient quickly

The dashboard layout helped users orient quickly

Our primary goal, the emergency button, was recognized as high-priority immediately

Our primary goal, the emergency button, was recognized as high-priority immediately

Our primary goal, the emergency button, was recognized as high-priority immediately

Users enjoyed horizontal scroll functionalities in the app, making time and scheduling more intuitive

Users enjoyed horizontal scroll functionalities in the app, making time and scheduling more intuitive

Users enjoyed horizontal scroll functionalities in the app, making time and scheduling more intuitive

Thinking beyond the picture

Thinking beyond the picture

Possible user conclusions we made

Novel apps reduce initial intuitiveness

The app progressively became easier to use, disproving the benchmark thesis

Lack of prior knowledge of the app limitation

Varied user mental models influenced expectations

Potential changes + Evaluation

COST IMPORTANCE TABLE

We prioritized and mapped out the costs for implementing ideas based on perceived value and importance

We prioritized and mapped out the costs for implementing ideas based on perceived value and importance

We prioritized and mapped out the costs for implementing ideas based on perceived value and importance

We pulled out the top 3 prioritized features:

We pulled out the top 3 prioritized features:

We pulled out the top 3 prioritized features:

Pain Points

Pain Points

Pain Points

Buttons difficult to click

Difficult finding portal info

Lack of familiar patterns

Opportunities

Opportunities

Opportunities

Increase button padding/add icons

Group similar, recognizable information

Include onboarding experience

Thank you again to Along With You.

Thank you again to Along With You.

The project was handed off in December 2025.

Thank you again to Along With You.

The project was handed off in December 2025.

The project was successfully

handed off

handed off

handed off

in December 2025.

Thank you for visiting :-)

Lexy Altieri © 2026